Has someone know how to update cache when release new version on PWA
I know can use localstorage to compare version string with api ,when restart the app will reload page and forceUpdate it
but what if user didn’t close the app just minimize it, and come back without restart?
Related
I uploaded my app to play store recently as .aab bundle with version code 3.6، after full rollout my app is succssfully published on play store, now my problem is that after publishing I discovered that the app is not working correctly with some locals eg "Arabic, Hebrew" so I created another aab file to fix the problem but unfortunately I forget to change the version number, to make the issue worse my workstation got corrupted hard drive and it's refusing to boot and my upload signing keys are not part of source control so I can't create new aab with 3.7 as version.
usually when the app is not published I can delete the release and then delete the appbundle from bundle explorer and reupload with same version.
Can I as desperate resort delete the app completely and reupload the same aab after creating new app?
Can I talk to google play store support and ask them to remove the release?
I tried to revert to a previous release 3.5 so that I can delete
the currently active one but with no luck
google play says I cannot revert to 3.5 because it doesn't allow users to upgrade!
Update: I just contacted google play support and asked them to change my upload signing keys, I had to wait for 48 hours until the keys became active.
I have a traditional Win32 desktop app written in C++/MFC that I have packaged as a UWP app for the Microsoft store using the desktop-bridge facility in Visual Studio 2019. It is currently published on the store, and users have been downloading it successfully.
I now need to release an update. I have incremented the Version numbers in the Packaging tab of the Package.appxmanifest and have a package just-about ready to submit to the Store. I hope (expect?) that current users will get their existing copy of the app automatically updated if they have set that choice in the Store app itself, or if they manually check the Store for updates. However, I am not sure whether that is actually true. Do I need to do anything within my program itself to make that happen?
Thanks for any help.
Yes, desktop bridge apps published in the Store update automatically.
I have an existing project which is live on some production server. There are a few users almost every time.
Front-end part is a SPA application (it's important)
On backend we have Maintenance mode which we are enable when we want to push our new features (it's bad because now we have a possibility to reach 0-downtime but it doesn't matter)
My question is: Which is the most correct way to do front-end production updating?
1) should we just remove old files and copy the new files to the production folder? (but in this case users might click on some link and the OLD BUNDLE will be fetched from server and we receive 404. Isn't it?)
2) Should we return some Notification Page (eg. Maintenance. Please visit our site later) while this process is running?
What alternatives exist?
Thank you for any help!
When I launch my receiver app on the chromecast device, it goes to the URL where my html is hosted to retrieve the receiver app to launch it.
However, when I update the contents of the HTML and JS sources on the hosted server and close the app on the chromecast, and relaunch the receiver app again, I often get the old version of the app and not the updated version that's already on the server.
I think this has to be some cache issue. I've disabled cache via the developer tools via the debugging port (9222), rebooted by device, created a cache manifest that tells it to cache nothing, it still wouldn't work, everytime I launch the receiver app on the device, it continually pulls the old version of the app from the URL.
Does anyone has any tips or solutions as to how I may force the chromecast to pull the latest version already on the hosted server?
thanks! :)
just a follow-up, when doing a curl on the command line, i'll always get the latest version. Just that the chromecast device keeps on getting the older version.
Open the DEBUG (javascript ) console http:// your chromecast ip:9222/ on Chrome browser while your receiver is visible.
Then enter the command window.location.reload(true); in the bottom of the console. This works every time I've tried it. It is also a good way to test broken session handling in your app as the refresh breaks any connections the page had setup. So it isn't perfect, but it will get the new content loaded.
You may also try adding
<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">
to your receiver page. In cases that I ran into this issues, rebooting the chromecast device had always cleared the cache.
HTH,
Ali
The Chromecast will cache the receiver if it's currently loaded. It will request a new Receiver if it's at the homescreen.
You can launch another app on your Chromecast then launch your Receiver again.
From the command line, you could do something like:
curl http://<ip of Chromecast>:8008/apps/YouTube
to launch the YouTube Receiver, then you could launch your own again.
I have a small solution that is composed out of 2 main projects a Mvc4 Web Api and a silverlight 5 Application. I've configured and deploy the application initially on the Azure platform and it all went great, but ever since when I deploy again the silverlight project does not get pushed and the online site has the old version.
I should mention all works great with the azure simulator on my local dev machine.
Anybody had a similar issue?
Regards,
I would suspect first (as Simon suggests) that the browser likely still has the previous client cached and loads that instead of downloading your new client.
You can use the version number in the code on your page that hosts the silverlight app to help. While it's easy for you to clear the cache - you don't really want to have to tell users to do that whenever you update.
Set the version to whatever your latest assembly version is (silverlight client project assembly), this will force the browser to download the client if the cached version is a lower number.
<param name="source" value="AppPath/App.xap?version=2.0.0.6"/>
Ok,
So after pulling my hair out, I finally figured out.
I have to change the build configuration to release in VS do a rebuild and then do publish because apparently the azure project does not do rebuild on the project when you publish it.
To solve this issue you'll need to identify the source of the problem (is it a client side problem where you have a caching issue or not). Even though you say caching isn't the problem we'll need to be sure about this first.
What I suggest is that you do the following first:
Activate Remote Desktop on your role
Connect through RDP and save this file to the role: http://support.microsoft.com/kb/841290 (fciv.exe)
Find the *.xap file (usually in E:\sitesroot) and get its checksum (using fciv.exe)
Modify the Silverlight project locally (maybe change a label or move around an element) to make sure its hash has changed.
Redeploy the application
Connect through RDP and use fciv.exe to get the checksum of the *.xap file once again
Compare both checksums
If the checksums are different, then it means that the deployment worked correctly and the Silverlight xap has been updated. If the checksum is the same, the problem lies with the deployment.
Please let us know the result so we can help you find the solution.