This is related to using the QA server with deploy URL or local host. On first start the URL is checked and then the app realizes it needs to switch to the QA server. That is still not working smoothly the first time and the original language bible fetch for the highlighting fails. On subsequent runs or restarts the app will default to QA server (persisted in local store) and selections will work correctly. The end-user will not have that problem since they are only using the production server - only those developers and testers will see the glitches.
Notes:
Doing Refresh will clear this initial glitch for a specific URL.
Clearing local storage and refreshing app will recreate the problem.
This is related to using the QA server with deploy URL or local host. On first start the URL is checked and then the app realizes it needs to switch to the QA server. That is still not working smoothly the first time and the original language bible fetch for the highlighting fails. On subsequent runs or restarts the app will default to QA server (persisted in local store) and selections will work correctly. The end-user will not have that problem since they are only using the production server - only those developers and testers will see the glitches.
Notes: