Open francardoso93 opened 1 year ago
I would like to provide additional information regarding the issue mentioned by @francardoso93.
Currently, we are utilising our customised instance of the mediator service in conjunction with a React Native App that employs the Aries Framework JavaScript version 0.3.3
.
This is how we configured the React Native Agent to work with the mediator:
const config: InitConfig = {
logger: new ConsoleLogger(LogLevel.trace),
label: `Agent1`,
autoAcceptConnections: true,
autoAcceptCredentials: AutoAcceptCredential.ContentApproved,
indyLedgers: [
{
isProduction: false,
id: 'bcovrin-test-net',
indyNamespace: 'test',
genesisTransactions,
},
],
walletConfig: {
id: `some_id`,
key: `some_id`,
},
mediatorConnectionsInvite: MEDIATOR_URL,
mediatorPickupStrategy: MediatorPickupStrategy.Implicit,
connectToIndyLedgersOnStartup: true,
};
const agent = new Agent({config, dependencies: agentDependencies});
agent.registerOutboundTransport(new HttpOutboundTransport());
agent.registerOutboundTransport(new WsOutboundTransport());
await agent.initialize().catch(e => console.error(e));
Note: MEDIATOR_URL
is an environment variable with the mediator url.
App is getting timeout when waiting response from mediator. Those are error logs for the mediator: