Vlad Murin

Results 32 comments of Vlad Murin

Have you tried this [solution](https://github.com/vmurin/react-native-azure-auth/issues/189#issuecomment-1660605272)?

And what happen after you close this browser window?

Try to replace `{applicationId}` in your manifest with a string literal and check if it helps.

If you don't have any variable or placeholder and just string there, double check the app registration - you should have the same `scheme/pathPrefix` in you callback URI.

Please check the answer below. I suppose it is your case too: https://github.com/vmurin/react-native-azure-auth/issues/94#issuecomment-656315746

Just try to use the additional parameter `redirectUri` in the initialization: ``` const azureAuth = new AzureAuth({ clientId: 'YOUR_CLIENT_ID', redirectUri: 'your redirect URI here' }); ```

> @vmurin Do you think it's ok to delete the `` if I use the `redirectUri` parameter in the `AzureAuth` initialization ? no, without intent the android OS will not...

Hey @HuiSF Thank you very much for your analysis. Exactly - that was the case - on one route the code was running as intended and on on the `/fetch-price`...

Additional V4 compatibility issue - the git variables. If something like `${git:branch}` is used it causes error: `Git provider is not found` (or similar)