I am developing an app based on winPho7 (no updated to 7.5 yet)
In my app, I call to a navigator to show a webpage but my problem is that (still testing)when I deploy the app in the phone, it shows the webpage perfectly.
But if I make changes in the webpage, the next time I open the app, it still shows the older one. My app doesn't get new images, new css, new buttons...
In Android I can delete cache and get the new webpage. How can I do it on winpho?
Now, I have to delete the app, install again and then, it will show the new webpage.
To prevent caching, add a random query parameter to the url, e.g. http://example.com/?ignore=425897425.
That will force retrieving the page again.
I hope that that is what you are looking for.
Related
When I load matchflix.ch on my phone, the installed app shows a different version than when I open the site in the phone browser. How can this be?
Details
I know that a service worker is in place for offline mode / caching. However, the web app should behave the same in the browser and in the installed web app, since in the service worker I only listen to the fetch event and do nothing on the install event.
Reproduction
You can check the difference by showing infos of a movie and then click on the yellow play icon. In the new version, it should show something below, while in the old version, a new website opens.
After a few hours, somehow, the version in the app is now the same as in the browser (as it should be). Still don't understand it really, but so far, the problem seems to be solved...
I successfully uploaded 2 windows apps to windows store. In the initial publish, I forget to select the windows store logos. So I update the app again with the store logo. But after completing the latest update still showing the default xamarin logo.
I created the windows app using xamarin forms and I set the store logo on the package.appxmanifest file.
Thanks in advance.
For windows store, some changes like store logo updation take up to a business week(or more) to be reflected in the store. That is the reason behind this issue.
I started using Parse-on-Buddy on the Buddy.com website recently. In the last couple of days, I am having issues trying to upload any kind of file to any of my classes using the web-browser. If I post a new object from the app I have built for it, the file uploads, but won't from the web. I have tried Safari and Chrome on my MacBook, both with the same results. I've reached out to support but without anyone getting in touch with me, and never answering their phone. Anyone else come across this issue and know a fix?
There is a known issue with dashboard file uploads and app keys, where if any app keys have been created, additionally there needs to be a JavaScript app key created for uploads to succeed. Create one by logging in to the Parse on Buddy dashboard at https://parse.buddy.com, navigating to your app, then going to 'App Settings' -> 'Security & Keys'. Click on the 'Create' button next to the 'JavaScript key' section. Thanks.
So I've lost the keystore file for my Xamarin App when my machine crashed. After cursing myself for not saving it, I've finally accepted that I need to create new app in playstore. I know I can unpublish an app in play store. What I wanted to know is, how can I tell the user to uninstall the old app and install the new one?
You can not change the old app in any way, so you are limited in what you can do and you can not force the users to do anything...
Personally I would not un-publish the old one at first, but it really depends upon the number of users and the reviews the app has. ;-)
If your old app has a number of good to great reviews and a better than avg. rating, keep it listed until your new app is at least equal. Google Play Store ranking algorithms use rating and reviews (among other things), so do not throw this away until your new app can match the old one...
You can update the old Application description in the Play Store without changing the .apk:
Add additional content to your old description that users surfing in the store should install the new app. Remember the first 167 characters are used in search results and becomes the metacontent so do not waste those characters...
Include a Url link in your old app description to your new app in the store (play.google.com). This link will be clickable in a browser, but not in the Play App on a device
Make sure to label your new app that is a new application as new and improved-style wording will catch the eye of a user in the Play Store
Also for existing users, make sure the your installed new app icon and name are different and standout from old app (you want to visually drive people to your new app once it is on the device)
If someone installs your new old and still has your old app installed, your new app can check via the PackageManager and prompt the user to uninstall it:
var pm = Application.Context.PackageManager;
var apps = pm.GetInstalledPackages(Android.Content.PM.PackageInfoFlags.MatchAll);
foreach (var app in apps)
{
if (app.PackageName == "com.sushihangover.SomeOldApp")
{
// Display dialog to tell user to uninstall old app...
}
}
If you old app has any New News section that you can publish content to, ability to receive a remote notification and display a message to the user, etc... make use of it to notify the user that there is a brand new app available via the Play Store....
Backup those new keys ;-)
When a user goes to my unlisted marketplace app page and installs my app the authorization popup window just white screens and doesn't close. If I manually close the popup everything moves on like normal. I have a suspicion that it's because my app is unlisted, since I haven't seen the issue with other marketplace apps, but as of right now I can't change that.
Another issue we've had with that page is the Integrate with Google button doesn't seem to respect the current profile the user is using. It always seems to always use the default profile which can be confusing for the user if they wanted to use a different google profile they were currently using.
note: the app url i've posted is used for local development but it happens on our production app as well