Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid DSN on expo setup on Andriod Emulator #286

Closed
97hknl opened this issue Oct 14, 2019 · 2 comments · Fixed by #287
Closed

Invalid DSN on expo setup on Andriod Emulator #286

97hknl opened this issue Oct 14, 2019 · 2 comments · Fixed by #287

Comments

@97hknl
Copy link

97hknl commented Oct 14, 2019

I tried to set-up the platform using the commands mentioned in the readme. Upon running yarn start, the app starts up on phone and prints Invalid Dsn with the following stack trace:

Invalid Dsn
SentryError
error.js:9:32
_fromString
dsn.js:40:42
Dsn
dsn.js:13:29
API
api.js:10:40
BaseTransport
base.js:10:34
FetchTransport
fetch.js:11:47
_setupTransport
backend.js:52:45
BaseBackend
basebackend.js:15:26
ReactNativeBackend
backend.js:12:8
BaseClient
baseclient.js:50:41
ReactNativeClient
client.js:15:25
initAndBind
sdk.js:15:53
init
sdk.js:59:16
init
index.js:159:27

App.tsx:36:14
loadModuleImplementation
require.js:331:6

index.tsx:17
loadModuleImplementation
require.js:331:6

AppEntry.js:4
loadModuleImplementation
require.js:331:6
guardedLoadModule
require.js:197:45
global code

@amaury1093
Copy link
Member

Thanks for the issue!

Can you try if #287 solves the issue? Make sure to run yarn start -c to clear expo's cache.

@97hknl
Copy link
Author

97hknl commented Oct 14, 2019

I found the fix. One must have to set everything to null, except the "waqiToken", which must be filled with your api key, and also "apiKey" & "googleMapsApiKey" which must be left as "YOUR_KEY" , basically a string, not a null. This fixes the issue for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants