-
Notifications
You must be signed in to change notification settings - Fork 158
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
Updated documentation for basic params/auth set-up for device + org id? #132
Comments
you don’t need this method. see the plugin api docs |
Thanks Chris. Yeah I figured I have tried this a few different ways and get an empty access token from the console server: Server side, I have set the following env vars: SHARED_DASHBOARD=1, ADMIN_TOKEN, JWT_PUBLIC_KEY, and JWT_PRIVATE_KEY... none of these seem to make a difference. And given no token, I'm of course seeing Auth Bearer not found in the server logs:
|
Why are you not posting your exact code to `findOrCreateTransistorAuthorizationToken’? |
here it is. I can post my entire test component as well if you'd like, but was trying not to overwhelm the thread here.
|
and....you got the exact code. Where is the answeer |
First, thank you for getting me up and running in a matter of minutes with your software. I've got a react native background demo app up and running using class components (based of this sample code)
I also have the background-geolocation-console app up and running on Heroku. I can log data to it, however I'm running into similar issues that others have posted regarding not providing the correct parameters as to take advantage of the device filtering dropdown + solve the sql lite errors.
The logs look like this
Based on other issues I've read and other comments, I've tried a few things to pass some of the filtering params through like,
passing params to ready()
params: BackgroundGeolocation.transistorTrackerParams(device)
-- my version of the lib says transistorTrackerParams is deprecated, and going this route doesn't make a difference (the code recommends using the authorizationToken approach here next).BackgroundGeolocation.findOrCreateTransistorAuthorizationToken
-- Unfortunately, I'm unable to create an authentication token going this route (I tried setting the SHARED_DASHBOARD and ADMIN_TOKEN env vars but still was unable to get a token from the server)Wondering if there's something obvious I've overlooked and/or if there might be updated docs you could point me to that might help solve this? Thank you
The text was updated successfully, but these errors were encountered: