Local dev apps no longer work | Community
Skip to main content

Local dev apps no longer work

  • September 14, 2022
  • 17 replies
  • 0 views

Siarhei

Hi,
I'm a developer of 'support' type app (ticket, user, org sidebars). Since today apps from the local environment are no longer available.
The problem is that apps tab is empty since today.
I'm trying to reach https://d3v-foobar4379.zendesk.com/agent/tickets/5?zcli_apps=true with the local dev server at http://localhost:4567 and I see empty apps folder. Yesterday my app was in the apps list tab, today this tab is empty

I'm using @zendesk/zcli/1.0.0-beta.23 darwin-arm64 node-v16.13.0 tools for serve local app.

I see in Chrome dev console that there are some issues and warnings.
1. Error with zendesk hub.html file

hub.html:1 Uncaught SyntaxError: "[object Object]" is not valid JSON
    at JSON.parse (<anonymous>)
    at CrossStorageHub._listener (hub.min.js:1:626)


2. Error with zendesk vendor file

vendor.a3b7dc240fac95aea.js:17521 Unknown initialization object: null Expected Object or Function.

3. Chrome can't load my local files because of CORB policy

Cross-Origin Read Blocking (CORB) blocked cross-origin response http://localhost:4567/app.json?locale=en&subdomain=d3v-foobar4379 with MIME type application/json. See https://www.chromestatus.com/feature/5629709824032768 for more details


I checked zcli profiles, tried to re-login, etc. 
Tried to disable CORB via Chrome feature flags - no luck.
Also tried Safari, Firefox - still no luck.

17 replies

Leafworks12

Hello Siarhei,

I have the same problems on multiple instances. Local development doesn't work at all, and all my team's developers can't work on apps. It looks like old zat tools still work, but our workflow heavily depends on zcli tools.

But, I have only Unknown initialization object: null Expected Object or Function. error in the console, and nothing else.


Eric27
  • September 14, 2022
Hey Folks,

We're digging into this and will provide an update once we've isolated the bug and put out a fix. 

Thanks for reporting!

  • September 14, 2022

Hello, my team and I are experiencing the same issues. Are there any updates to this problem? 


Martin25
  • September 14, 2022

Hello, Same issue here.


Pat12
  • September 14, 2022

Same Issue here, hope to hear back soon!


Theo18
  • September 14, 2022

We're experiencing the same issue, would be great to get a fix soon


Phil19
  • September 14, 2022

I too am running into this issue.


Donny13
  • September 15, 2022

Same issue as well.


  • September 15, 2022

Having the same problem also. Difficult to deploy any changes at the moment in case it breaks things.  Was a great feature when it was working!


Zach22
  • September 15, 2022

Hi everyone, we appreciate your patience as we've been troubleshooting the issue. We identified the source of the bug and have rolled out a fix. You should now be able to resume testing apps using the local development server with ZCLI.

Please let us know if you are continuing to experience issues.


Leafworks12

Hello @zach22,
I still have the same problem for some locations in manifest.json. Here, what I have in my app, and it doesn't work:


"location": {
"support": {
"nav_bar": {
"url": "assets/index.html#location=nav_bar",
"autoHide": true
},
"ticket_sidebar": { "autoLoad": false },
"new_ticket_sidebar": { "autoLoad": false },
"background": {
"url": "assets/index.html#location=background"
}
}
}


I played around, and found two cases when it works:

"location": {
"support": {
"nav_bar": {
"url": "assets/index.html#location=nav_bar"
},
"ticket_sidebar": {
"url": "assets/index.html#location=nav_bar"
}
}
}

"location": {
"support": {
"nav_bar": {
"url": "assets/index.html#location=nav_bar",
"autoHide": true
},
"background": {
"url": "assets/index.html#location=background"
}
}
}

It looks like apps with location  { "autoLoad": false } break local development.

Best regards,
Andriy


Leafworks12

Hello @zach22,

Any news on my last comment? I see this topic has Answered label now, and I don't want it to be missed. But unfortunately, the local development is still not working for almost every app for my team, so we are forced to use zat tools. 
It breaks our development process, which relies on zcli tools, and adds a lot of frustration to work. 

Best regards,
Andriy


Eric27
  • September 19, 2022
Hey Andriy,

Mind if we move your issue into a ticket as it seems to be a separate bug from the rest of the thread? 

Thanks!

  • October 9, 2022

Hi Team,

I am still facing the issue.

I am using windows wsl and zendesk sandbox. My version details are as following:

root@XXXXXXX/zendesk-shell# zcli --version
@zendesk/zcli/1.0.0-beta.24 wsl-x64 node-v14.17.3

Error:

 Access to fetch at 'https://xxxxxxxx.zendesk.com/agent/tickets/' from origin 'http://localhost:4567' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

 


Eric27
  • October 10, 2022

Hey Sahib, 

That doesn't look to be related to the local server bug. Are you using secure settings by chance?


  • January 25, 2023

The same issue is happening again. Exactly what is outlined in the first post of this thread. Please assist. 

 

Thanks,

Roger Larsen 


Greg29
  • January 25, 2023

Hi Roger! The issue today is separate from what is happening here. Please see this post for more details.