Having some difficulties setting up our app for the UI extensions beta. Basically, I ran hs project migrate-app and converted over our staging app to use the new UI extensions beta (public). I’ve made changes, added an extensions directory and the proper modifications to our public-app.json but every time I run `hs project upload`, it fails with:
No supported components were found in this project. Run `hs project add` to see a list of available components and add one to your project.
Press ‘q’ to stop the local dev server
--------------------------------------------------
[INFO] Running extension ‘Hello Public App’ from app ‘xxx’
[WARNING] Couldn’t find the following components in the deployed build for this project: ‘[UI Extension] Hello Public App’. This may cause issues in local development. To reflect these changes and continue testing:
* Stop `hs project dev`
* Run `hs project upload`
* Re-run `hs project dev`
This happens even if I just fetch the latest build and try to upload it (with or without makes changes to support the getting started example extension). I can verify that my extension is setup properly (using the example getting started component), with the proper changes made to public-app.json. Would love some help trying to debug!
Hi @Tamzin Welcome to our community! Thanks for sharing your details and the steps you’ve already taken. I’d like to invite some of our community experts to the converstaion — hey @zach_threadint@dsmarion@tjoyce, do you have any troubleshooting tips for @Tamzin?
@Tamzin - I’m very sympathetic here. I just spent a frustrating 3-4 days tying to learn the basics of this myself. I succeeded in the end to deploy an almost trivial sidebar card (38 builds), but the framework to set this up is both arcane and very fragile. [I’ll stop here before I go into a rant].
I’m think you have propably already tried this, but it seems necessary to work though the tree of files that point to one another and make sure all the dependencies line up 100% correctly. The top level file - as I think about it - is the hsproject.json where the project name and file details need to cascade correctly through app.json and extensions/your_name.json & extensions/your_name.jsx at least to start. You may be able to find your error as you work backwards and forwards with the quick start example - IMHO way more complex than it needs to be.
NB. I gave up on the local development server - I could not see the point of more infrastructure to debug. You get a fair amount of run-time information in the private app details when you actually get something to upload.
Hey all - I ended up finding out the issue. The problem was that I had my downloaded project in a hidden dot folder, and I found that making the included folder not hidden it fixed my issue. We built some scaffolding on top of HS to share code between projects so the goal with the hidden directories were to help fascilitate the facade. Hopefully this helps anyone else who might encounter this in the future
Welcome to our community! Thanks for sharing your details and the steps you’ve already taken. I’d like to invite some of our community experts to the converstaion — hey