I have an app on the google play store that's getting around 3k downloads a day. Recently I tried sharing my files through google drive and they all got screwed up and won't work in Android Studio when I open them. Is it possible for me to start from scratch and submit that update to the listing I already have? All I'd like to do is place some ads into the app
I still have the key for the file I believe.
Thanks for any help in advance!
You can still sign a new version of the app so long as you have the original key and passcode (if you used one).
Submitting successfully will also require you to have the same package name and a version number higher than your last release.
Was able to find the answer! Turns out I can create a new android studio project with the same package names and sign with the old key.
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.
Writing an android application. It has no errors when I run it on an emulator. But when I tried to build it to an apk file to test on a device, I get the following error.
com.intellij.openapi.project.IndexNotReadyException: Please change caller according to com.intellij.openapi.project.IndexNotReadyException documentation
at com.intellij.util.indexing.FileBasedIndexImpl.handleDumbMode(FileBasedIndexImpl.java:853)
at com.intellij.util.indexing.FileBasedIndexImpl.ensureUpToDate(FileBasedIndexImpl.java:802)
at com.intellij.util.indexing.FileBasedIndexImpl.ensureUpToDate(FileBasedIndexImpl.java:786)
at com.intellij.psi.stubs.StubIndexImpl.processElements(StubIndexImpl.java:250)
at com.intellij.psi.stubs.StubIndexImpl.processElements(StubIndexImpl.java:238).......
I seen one similar case raised here which mentions to "Wait till indexing is complete."But I am not sure what I am doing to even interfere with any indexing.
Tried on different computers. Same problem. The only thing I did different before I got this error was to add a dependency at gradle(app) for a RingButton and added that RingButton class to the project to modify it to what I wanted.
As I said it is working fine in emulator.
Just to test if that is indeed the isse, I deleted the class and removed the dependency but the issue is not resolved.
I think this can be solved by creating a new project and moving the files into the new one. Maybe the index is corrupt. But before that can you clear the cache ? in android studio if your prepared to lose some local history then try this:
and then chose invalidate and restart:
I was using Dropbox to constantly backup my project every now and then. So I would click my project and send to Dropbox. I was also instantly clicking run to run the app on my emulator at the same time. During this period, when I mouse over my Dropbox icon, there is an indication that it is "Indexing".
Based on previous answer "Wait till indexing is complete", I can only assume this Dropbox indexing interfered somehow.
Not exactly elegant but I copied each and every file in this project into a New Project and everything is working fine now and able to install the apk file. I didn't change anything so I believe there is some form of corruption in the old project.
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.
My development account for Spotify has been enabled and I am trying to walk through their simple tutorial app (http://developer.spotify.com/download/spotify-apps-api/tutorial/). I should note here that I am on a Win 7 workstation.
When I try to load the local app by typing 'spotify:app:Tutorial' in the search field I get the following msg/error: "Sorry, I could find this app. metadatafailed URI: spotify:app:Tutorial Error: appNotFound."
I have tried adding the app files to the following directories and still getting the error:
C:\Users\Me\Documents\Spotify\Tutorial (note this dir did not exist I created it)
C:\Users\Me\AppData\Local\Spotify
C:\Users\Me\AppData\Local\Spotify\Users\me-user
C:\Users\Me\AppData\Roaming\Spotify
C:\Users\Me\AppData\Roaming\Spotify\Users\me-user
So where exactly are you suppose to add the files so that Spotify will load local apps?
Thanks!
Your first guess is correct (C:\Users\Me\Documents\Spotify\Tutorial). However you need to be running the latest preview release (https://www.spotify.com/uk/download/previews/). And on my PC I had to completely un-install and reinstall the application before the developer options became enabled.
Not sure whether it helps in your case, but try naming the folder tutorial with lowercase t. See Spotify Tutorial example app is blank
I can't leave a comment, but I was having the same issues and had to do a combination of what Niklas and akakjs did. I had to completely uninstall the spotify app, download/install the preview version, create a Spotify directory in My Documents, then create the folder Tutorial. Then, in the Spotify search bar I had to type "spotify:app:tutorial" with the lowercase t. I hope this helps!
Had the exact same problem. I had to run Spotify as administrator, worked right away.
And the path i used were: C:\Users\me\Documents\Spotify
I had the same problem: Spotify could not find my app directory even though the proper folder had been created in my Documents folder.
I Fixed it by running Spotify as an Administrator.
I have recently upgraded to the new Azure SDK (September 2011 v 1.5).
Ever since I have not been able to start the compute emulator. Consequently I can't debug the services on my local machine.
I have seen a suggestion that the problem lies with the fact that my user account has a space in it, so I renamed my account but that didn't make any difference. It may be that the problem is that my user profile path has a space in it. Changing the account name has no effect no the profile path.
On the msdn forums it was suggested that I remove *:808 binding in IIS Manager for Default Website. See MSDN Forums
Anyone have any other ideas?
Another option:
So, given the "rename your user account/regedit doesn't work for you, you may want to look at this MSDN article, which suggests you can just set an environment variable and run the emulator without mucking with the registry... not sure if setting the environment variable globally would let you run automatically within VS.NET without manually starting up the emulator the first time, but it is certainly easier.
Yes, the space(s) in your profile path are the issue, and this appears to be a regression for a bug that was found in a previous version of the emulator (the only reason I even thought to try logging in with a different account in the first place). I was literally just putting together a quick blog post here describing the same issue. You'll need to do some registry editing to fix all the references to your old profile path if you want to fix it, or just create a new user if you can deal with re-installing software (I love the Web Platform Installer, but I found out during this exercise that it doesn't do a good job installing for "all users").