• Erica Girges

  • January 12, 2023 20:07

  Zendesk Developer Advocacy

  Hi Nicole,
  Is there a refresh on any of the ticket tabs happening before this error is received?
  
• Nicole Pan

  • January 13, 2023 15:31

  No, there isn't a refresh. This happens when I click to go to a different ticket tab, without doing any other actions.

• Erica Girges

  • January 17, 2023 19:02

  Zendesk Developer Advocacy

  That definitely isn't expected behavior. Let me go ahead and pull you into a ticket so we can get a better look at your instance and the app. 
   
   
  
• Nicole Pan

  • February 08, 2023 18:00

  Hi Erica, wanted to follow up on this because the ticket was closed out.
  
  I'm not sure I understand what you are saying about the instance Guid and app Guid.

  I was doing some testing on our side and noticed that:
  

  1) when a new ticket tab is opened, an "instance.registered" event fires, and each new ticket tab has a different instance Guid. The appGuid is the one that seems to be created only once.

  2) each instance is associated with an active ticket. To get the active ticket, we need to get the instance client, which we do by calling appClient.instance(instanceGuid). There is no way for us to get the activate ticket with only the appGuid.

   

  I only get the error when app.deactivated fires, but when the event fires, all of the instances are registered (including the instance that is logged out).

   

  Is it possible to set up a call to walk through this? 
• Erica Girges

  • February 14, 2023 18:24

  Zendesk Developer Advocacy

  Hi Nicole!
   
  Of course. I'll go ahead and open a new ticket with you so we can dig into more.
  

Please sign in to leave a comment.