In app purchases on my app have worked fine for 2 years, and I think they are still working okay in Google Play with actual purchases. But recently when using promotion codes, or internal/beta testing, when I try restoring a purchase, I get the following error:
Error - you already own this item
If I try to purchase an item, it looks like the purchase flow works properly. But then once it is done, I get the same error above. And I can’t restore anymore.
I’ve tried all the advice out there on resetting Google Play/Services Cache, and this person several years back seemed to have a similar issue that was never solved Error You Already Own This Item. Most other discussions on this topic are fairly old and outdated.
One strange temporary fix is that if I revert my Google Play store to factory settings (I'm on a slightly older 3 year old device), it will work again... until Google Play store updates, and then it stops working.
I was using this library successfully https://github.com/anjlab/android-inapp-billing-v3, but I thought maybe since it is outdated this might be the issue. However, doing it even without this library (using official Google documentation on setting up IAB) still results in the same problem.
Does anyone know how to fix this?
Thanks!
For issues with the Google Play Billing Library I would suggest filing a bug on the public issue tracker listed at https://developer.android.com/google/play/billing/contact.
I have a field service reporting android app that I created in Oracle MAF. it has been in use for almost a year now with no UI issues, Over the last few days, I have been getting reports from our end users that the button text is disappearing. so - anywhere where there is a button with text inside it, the text is not visible. same font is being used elsewhere in the app with no issues. All the end users are running this on the Samsung Tab A 8.1. The last android update for the device was a few weeks ago. The problem is slowly propagating, like only 4-5 users a day are reporting that they go to use the app and the text is gone. luckily they are used to the app and know what all the buttons do, but I have to eventually fix it. I can't get any straight answers from Our IT department or Samsung as to why it is happening like this, and the update didn't seem to have anything in it that could do this. A factory reset fixes it for a day or two, and then the issue comes back.
What it is supposed to look like
Example of missing text
Like I said, this has been working fine for a while now. I'm mainly looking to see if anyone is aware of an Android update that would cause this, or if there was anything in the Samsung security update that would do it.
Google pushed an update to Chrome that they have discovered caused problems like this, and many others.
I was able to instruct my end users to disable chrome and let it roll back to the factory version.
this fixed the issue.
I have a problem when call ends, and finish() to current activity of conversation, app blows me, but does not show me any error, and often appears me this error:
E/TwilioConversations: [Signaling]:RESIP::TRANSPORT: Got TLS read ret=0 error=6 error:00000006:invalid library (0):OPENSSL_internal:public key routines
If someone could help me because I have a lot of time with this problem.
Do you have other 3rd-party libraries that use SSL? There may be a conflict between the Twilio Video SDK and another library.
I have also seen this resolved by ensuring that you have the latest version of the SDK installed.
However, if you can let me know any more specifics regarding your code, I'm happy to help debug further.
I am new to java and android and wanted to see how developing for android works
I started by downloading the SDK FROM HERE
However after I finish making the Hello World project sample given in the website HERE, if I try to run it on the emulator as explained HERE, the emulator screen appears, but nothing seems to happen. I can see the word android on the middle of the screen with some animation happening, but that's it. The website says something about unlocking the emulator, but I have no idea what that means. What I have gathered from reading other posts is that the emulator is supposed to have some kind of slider switch as in real smart phones which should be dragged to unlock it, but I can't see it in my case. Now I have no idea why this is happening or what I should check out in order to fix this. Are there any installation logs or something else that I can check to see what the settings are?
What I have tried till now:
I downloaded the SDK ADT bundle from HERE and just unzipped it. Then looked for eclipse.exe and ran it directly. Is there anything else I should have done prior to this?
When I did it for the first time, I had only JRE installed and not JDK, which I realized after reading THIS POST. So I downloaded JDK from HERE, updated the required environment variables and restarted eclipse, but still it's the same thing.
I looked at the Eclipse isn't talking to the emulator section GIVEN HERE, but all it says is to restart eclipse and the emulator, and it doesn't do anything at all.
Rant:
I can understand if the program had failed to compile when I didn't have JDK , or if the IDE gave any indication at all of a faulty program install, but that isn't the case. Everything seems ok, there are no errors, but it just doesn't do anything. This is the type of thing that makes people pull their hair out, and personally, I think the With a single download, the ADT Bundle includes everything you need to begin developing apps: in the android website is very misleading, especially for complete beginners
Anyway, what should I do to make the tutorial program run on my computer? My computer is a bit old and slow so could that be an issue? My computer is Windows XP SP3 on Intel(R) Pentium(4) 4 CPU 3.20 GHz 3.19GHz 2.50GB RAM, but if that was the case I assume the emulator shouldn't even start up
You just have to wait a bit longer. Android loads pretty long on emulator.
Tutorial says about unlocking, because when Android is loaded, your screen on emulator will be locked.
If you find emulator too slow for you, you may want to check this topic out: Why is the Android emulator so slow? How can we speed up the Android emulator?
I had the exact same problem as you when I first got into Android development a week ago. The two things I did are simply
1) Set the usable RAM on your AVD to 768MB
2) When you run your Hello World program in your emulator, give it about 5-10 minutes. Don't touch or click the window at all, just let it load up. Later you can make it persist
3) If your home screen comes up, click and hold the mouse button in the center of the screen, then drag towards the sides and release, this should unlock the device.
Try these steps first, if they don't work then there is likely a problem with your AVD configuration.
If you are launching your app first time with emulator, it will take appropriate time.After that, on Lock icon click and slide to the right. then you can view you application. If not check for your app(icon) installed.
By seeing your configuration of PC I think it will take some time to load emulator. After emulator is load (see below image)
then and then run your code and also check in eclise-device that whether emulator is online or not.
For checking emulator in eclispe :
In second image just above windows logo you can see small rectangular button with plus sign click on that you will get list from which you can select devices. You can find similar button in you eclipse at the bottom.
I had the exact same problem and followed the exact same steps, but was also unsuccessful. I ended up creating a new AVD with a Nexus 4 instead of the latest Nexus 6. The resolution of the 4 is much lower, which I think is what solved my problem. It loaded much more quickly using the 4.
Also, When I was using the 6, I could only see "ndroi" because the size of the screen was much larger than the size of the phone. Now I can see the full device.
vs.
You may just need to relaunch the Android studio 3.6.3.
I got a similar problem. The hello world app does not install on the emulator.
Problem solved after relaunch.
I've been banging my head against Midi on the Android SDK all day and, although I have music running through the JetCreator all right, there's still an issue where certain notes on certain instruments just aren't playing. It almost sounds like the octave range is capped or something.
My general hypothesis is that the default DLS file android uses doesn't support a full range of octaves...or something like that. I tried importing gm.dls from the Windows install into the jetfile but I had the same problem so maybe that's not it. Programmatic music is very new to me. There's very little user-developed documentation or help in this regard...apparently DLS is really old and everyone uses soundfonts now....which begs the question why does JetCreator still use DLS?
Anyways I'm looking for a little guidance from someone who's familiar with the library.
Given your comment, I'm guessing that you probably tried to queue too many notes to the instruments at the same time. Did you manage to get the issue fixed?