You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you install more than one build flavor of OBA (e.g., obaGoogle and obaAgencyX), and then try to log in with embedded social, you get prompted to associate the login with more than one application. I believe this is due to the hard-coded value com.joulespersecond.seattlebusbot for package_name in onebusaway-android/google-services.json. This should be dynamically changed to reflect the applicationId defined in build.gradle. For example, for Agency X it should be org.agencyx.android.
Screenshot:
Related to #853, as to fully support independent ES profiles per build flavor, each build flavor also needs it's own Embedded Social API key.
Steps to reproduce:
Install both the obaGoogle and obaAgencyX build flavors
Open obaGoogle (i.e., normal) OBA app
Go to navigation drawer and tap "Log in"
Tap "Google"
Expected behavior:
Take me straight to the Google OAuth screen on behalf of the normal OBA app
Observed behavior:
It gives me the option to handle the action using either the normal OBA app or the Agency X app
Device and Android version:
Samsung Galaxy S8+ w/ Android 8.0 beta
Screenshots:
See above
The text was updated successfully, but these errors were encountered:
Summary:
If you install more than one build flavor of OBA (e.g.,
obaGoogle
andobaAgencyX
), and then try to log in with embedded social, you get prompted to associate the login with more than one application. I believe this is due to the hard-coded valuecom.joulespersecond.seattlebusbot
forpackage_name
inonebusaway-android/google-services.json
. This should be dynamically changed to reflect theapplicationId
defined inbuild.gradle
. For example, for Agency X it should beorg.agencyx.android
.Screenshot:
Related to #853, as to fully support independent ES profiles per build flavor, each build flavor also needs it's own Embedded Social API key.
Steps to reproduce:
obaGoogle
andobaAgencyX
build flavorsobaGoogle
(i.e., normal) OBA appExpected behavior:
Take me straight to the Google OAuth screen on behalf of the normal OBA app
Observed behavior:
It gives me the option to handle the action using either the normal OBA app or the Agency X app
Device and Android version:
Samsung Galaxy S8+ w/ Android 8.0 beta
Screenshots:
See above
The text was updated successfully, but these errors were encountered: