Hub: C-8 Pro
The Issue: My package manager said there were updates available; specifically Inovelli, and Google Calendar etc. I select both, and then the only button visible is "Main Menu". There is no other button visible. if I click that, it throws me back to - you guessed it - the main menu page.
How do I get the updates to do their thing?
Thanks, gang!
I see the same thing running Chrome on my Android tablet.
After selecting the updates you want, try clicking on a blank area of the screen. At least that works for me.
Edit: I also have to rotate the screen to portrait in order to see the "Next" menu item at the bottom of the page.
Not seeing that here. Just updated an app earlier today.
Sounds like you may have a browser cache issue. Clear your browser cache and/or try a private/incognito browser window.
I cleared the cache.
I then clicked in a blank area, and the "Next" button appeared.
All is working.
Thanks, everyone!
(HUB: C8 Pro)
I am not getting that issue, but I am getting this issue often:
Sometimes the updates go through. But I see this message quite frequently.
Any ideas?
Do you mean you see that message about CoCoHue udates, or in general about other updates as well?
Have you tried clearing your cache on your browser/using an incognito mode browser tab?
I see that about every update that is available.
I have tried clearing the browser cache, but still am running into the issue.
I am on HPM Current Version: v1.9.11
It does seem that if I do a package repair, it will update at same time, but this seems like an extreme option.
Make sure logging is enabled, and run HPM again, when the error occurs post the error and logs for the error.
Generally best to post in the app's release topic, where the dev managing HPM will see it (along w/other HPM users).
Also tagging @bertabcd1234 since it's his app.
Thanks for that. I could not find the app release topic, but found this thread instead.
What is the actual error from Logs?
That being said, if it sometimes works and sometimes doesn’t (for the same package), it’s unlikely to be an issue with the package itself.
