search

Sitata / issue_tracking

This repository is used for issue tracking with Sitata's clients
0 stars 0 forks source link

Additional Destinations not showing for hospitals, safety, emergency numbers #16

Open seanflynncontact opened 7 years ago

seanflynncontact commented 7 years ago

When multiple destinations are added to the trip builder they are not being displayed for SITATA options of hospitals, safety, emergency numbers.

johnmeade commented 7 years ago

Do you mean that the new countries that are added via trip builder do not appear in some of the Sitata activities? Emergency numbers should have a list of all countries available, regardless of whether they are a part of the user's itinerary. What steps should I take to try and reproduce this? Did you do something along these lines?

  1. clear all trips for your test traveller using the traveller or partner API (or create a new traveller)
  2. clear all data on the mobile device for the test app (uninstall is safest)
  3. create trip for your traveller
  4. open app and trigger sync process
  5. wait for current trip and list of countries to sync using the WaitForCompletion methods
  6. launch trip builder
  7. add several countries and cities (which destinations did you use here?)
  8. click "finish"
  9. launch safety section
seanflynncontact commented 7 years ago

This is reported by QA. I'ts happening on Sitata landing page after the new code that waits for current trip to sync. Shawn reported it happens after adding new destinations via initial trip builder as well as edit trip. He reported it happens even after going out of the page and back into the page (we perform the new sync process going back to the page)

johnmeade commented 7 years ago

We could not reproduce this in either the Android or iOS SDKs. We tried to exhaust as many ways of using trip builder as we could, we both saw expected results. We tried various permutations of:

After these tests, the GUI screens (safety, hospitals, alerts, ...) seemed to behave properly for us and contained the correct countries. Do you think you could try to reproduce this issue from a clean state (uninstall mobile app, clean build app)?