Ic-reactor read_state,preview:subnet_not_found

Developers JavaScript
1

image

image
image730×129 3.35 KB

Can I turn off this read_state using ic-reactor? My canister can be used directly locally, but it will fail when read_state is used.

2

This read_state probably is firing when you are attempting to make a call to an update function in your backend canister from your client. Are you attempting to make a call to an update function?

I do not think that there is a way to remove this.

CC: @b3hr4d (for ic-reactor)

2 Likes
3

Hello, I am using Ic-reactor library to initialize canister, it will call read_state method and get error 403, what could be the cause of this problem? I was using Connect2ic/react which doesn’t seem to have a read_state step, but canister works fine.

image
image753×110 2.74 KB

4

Hey, Can you share the code? How did you initialize and calling function?

1 Like
5

The local agents are connected first
image
Then we create the Actor
image
Finally wrap my App with Provider
image
And now I have

image
image1685×396 13.6 KB

6

bd3sg-teaaa-aaaaa-qaaba-cai Where does this canisterId come from :disappointed_relieved:

7

In the above error, I did not call the read state method actively.

8

Do not need to use createAgentManager and AgentProvider at the same time, just pass the arguments into the AgenProvider and it will take care of agent behind the scene.

9

This is DidJs canister that will exist on dfx that power candid-ui and we will use it to convert downloaded did file into execuytable javascript file

This proccess can be ignored if you pass idlFactory from your canister declarations!

10

image
I replaced this, and I went back to the 400 error

image
image1478×560 40.7 KB

11

image

image
image1527×640 47.7 KB

12

You might be missing something on the project setup, is this vite?
Take a look at the examples or this next-template or this vite-template
This error is no from @ic-reactor/react anymore, those are about how your project handle API calls.

13

Okay, I understand. Thank you for your reply~

14

Pass the idlFactory if possible, and use CandidAdapterProvider when you dont have access to the declarations files.

import { idlFactory, canisterId, vault_factory } from "../../declarations/vault_factory"
import { createActorContext } from "@ic-reactor/react"

export const {
  ActorProvider: VaultFactoryProvider,
  useActorState: useICPLedgerState,
  useMethod: useVaultFactoryMethod,
  useQueryCall: useICDVQueryCall,
  useUpdateCall: useICDVUpdateCall,
} = createActorContext<typeof vault_factory>({
  idlFactory,
  canisterId: canisterId || "aiqu4-ruaaa-aaaaa-qaqaa-cai",
  withDevtools: true,
})

And if you get stocked, share you repo and I will help you with the setup.

1 Like
15

Wow, great. I’m very happy to have your guidance. Would tomorrow be all right? I have some other things to adjust today. :blush:

16

No problem :slight_smile: Happy to help you getting started with ic-reactor library.

1 Like
17

The experience of using ic-reactor is very good, my mood has become more pleasant and everything feels more controllable. And thank you very much for helping me! :rose: :rose: :rose:

1 Like
18

image
Hi, buddy. Long time no see. I’m having a bit of trouble now, he’s repeatedly triggering userPrincipal when I’m not logged in. Are you free now,share my repo give you? :smiley:

19

Yes, I have time now!

20

Great, I invite your github to join