– resolved – the full debug url needs to be revised in 3 diff places
- the get url calling spotify authorize
- the api connector’s call for ./api/token where in the body there is prop redirect-uri
- the spotify api dashboard’s list allowed callbacks
if they all agree then the callback from spotify starts the bubble debugger
scenario - standard protocol in 4 stps for oauth 2.0 to authenticate and to then use auth-code to get an access token. My implementation follows sample youtube clip that takes Spotify authenticate as the example ( below )
Note that i want debug=true when the 2-step WF process gets the access-token returned by Spotify, using the AT in a call.spotify.List(my artists ) . Everything i have tried results in NO debugger when the app returns from the 2 step auth process. I think that data call to spotify is returning a json.array as called for by the API Connector .
unfortunately , without debug , SOL in resolving any issues. Also these types of data calls (within Bubble runtime) can not be seen by devtools.network tab.
How to get debug = true following the callback step of oauth dialog???
In JS syntax, all i want todo is to on the callback , is to add the following query to location.href and refresh …
*debug=true*
in the img , my issue arises after steps 3,4 when i have the access token and make the call ( spotify ) to return Artist list ( see below )
note debug=true query portion of the callback URI…
WF step 2 retrieves/ uses the access-token to get a LIST from spotify.
there is the Connector call using the Access-token value
And when oauth is complete and control returns ( a callback GET made by Spotify on
redirect_uri=https://api-rr-spotfy.bubbleapps.io/version-test/index&scope=user-follow-read&show_dialog=true&deug=true
bubble runtime when code not empty is invoked to get the auth-code from the url and note that debugger is set to trap the onCode condition
despite all that, There is NO debugger…
