Open HamzaBinSarfraz opened 4 years ago
Thank you for reporting, we're aware of the issue and working on a fix. In a few hours the patched version of the app will propagate through the app stores.
This was fixed in #204
Why was this fixed in uport-mobile
? Will this also be fixed in ethr-did-resolver
?
The problem was uport-mobile was using an old version of ethr-did-resolver
that used a hardcoded RPC url. The url format was deprecated by infura and is now throwing an error.
This was compounded by a wrong architecture of the legacy versions of the DID-resolvers which expected to be registered globally. The global registry was being overridden by other library initializing with defaults.
The latest version of ethr-did-resolver
accepts a configuration and is also no longer registering as a global but expected to be supplied into a Resolver
instance that gets passed to verifyJWT
.
The hardcoded URL in ethr-did-resolver will most likely go away and require developers to supply either an RPC url (like infura) or their own provider
i am scanning QRCode from uport landia website https://uportlandia.uport.me/city but after scanning nothing happens on mobile app,. previously it show me the requested params from uport landia request