Countly cached app key in browser somewhere and is ignoring if it is changed to new key.

Countly cached app key in browser somewhere and is ignoring if it is changed to new key. If i create, in admin console, new app, Countly ignores that i am now passing new app key and sends old app key in requests to server. Yet in incognito mode in Chrome everything works fine. How to handle this case?

0

Comments

2 comments
  • Hi Andrii,

     

    This can happen if the old app key is stuck in the queue. First thing to check is if the SDK you are using is up to date, if a new one is available please upgrade to the latest.

    To solve this problem you can either clear the queue using

    Countly._internals.clearQueue()

    Or, as you have changed the app key, you would want to start clean for all users, so you can just use new namespace, which will use clean storage. 

    clearQueue should work for you, but others users could be affected. Trying another namespace in the sdk init should solve problem for all users. Please let me know if you have more questions.

     

    0
    Comment actions Permalink
  • Thank you for your quick answer, so should i issue new release of my app with 'Countly._internals.clearQueue()' triggered after countly init event triggers? can i keep it there to avoid multiple releases?

    Also, seems like it is working now locally on my pc. Yet we might play around with apps in future for different env's and this means app keys might change(yet i know we are able to keep current keys, just modifying DB with old key).

    0
    Comment actions Permalink

Please sign in to leave a comment.