Session token for android and ios isnt properly set

[mustafaezzeldin2020]

after setting newSessionKey to false, to use same session token. this increased our billing.

After debugging session tokens it's noticed that the old session token is never updated.

Current behavior: the autocomplete session token and places details token are the same even after fetching place details

Correct behavior: the sdk should use token per session meaning that the token should remain the same until fetch details is called, then a new token should be generated for the next search session. so, each search session token should end by calling fetch place details and not to use the old token

please this needs to be updated to avoid extra billing

[Roman-Diachenko]

Hi @mustafaezzeldin2020 Try to play with the newSessionToken bool param for the findAutocompletePredictions method.

From the Google doc:

The session begins with a call to Autocomplete (New), and concludes with a call to Place Details (New) or Address Validation

When you begin the session set the newSessionToken as true and change it to false until user select a prediction (so all request under same search will be associated with one session) and call fetchPlace method subsequently (to complete the session) and again set newSessionToken to false