I've published a beta of my app in Google Play.
I can see it with my smartphone and I can install it with a different account from the developer account (just to be sure).
Now I try the same with an 'old' tablet (Android 7.0, Google Play 6.1.12) and if I click on the link to the app:
https://play.google.com/store/apps/details?id=com.infinitymundi.anima
it tells me 'element not found':
if I try to cut and paste the link in the browser it shows the app:
It even shows the Install button, but if I click it gives me 'element not found' again.
My app is built with Unity and it's compatible with Android 6.0+ (I deployed the same app in this tablet with Unity and it worked).
Any suggestion?
Thanks!
I've found out that you need to download an unofficial google play services update from here https://www.apkmirror.com/apk/google-inc/google-play-services/ and it worked.
Maybe this is strictly related to my tablet model (a Xiaomi).
It will be useful for others, I think.
Related
My app-ads.txt tab in Admob console not showing anything Even though I've published two apps on Google Play. I've waited Weeks but no update.
Please help me as soon as possible, I am frustrated and I am very tired of searching a lot on the Internet about the problem and I did not find any solution or even a description similar to this strange problem.
I was having the same problem for some time now, app ads text file was not showing for one of my app in Admob, but for other apps it was visible.
Solution: Today, as I was checking the store settings of my app I realized that I was using a social media link in the place of website. I changed it immediately to my website.
After 10 minutes or so when I refreshed the Admob App Settings page, it found my app ads text file successfully.
Hope that helps!
Only linked apps (Linked to a store) will appear in app-ads.txt tab in AdMob console.
This is how to link an app in AdMob to Google Play:
Go to AdMob console
Select the app you want to connect
Go to app settings from the left menu
Click on ADD from App Store section
Search for your app name and Add it
IMPORTANT Note: you can not unlink your app later so PLEASE be careful and make sure that you are adding your app and not another app.
now it may appear immediately in app-ads.txt tab in AdMob or it could take up to 48 hours
I have developed an app and integrated with Admob using cordova-admob-free. It works fine when the release apk is installed to any device (test or not). It also works when the app is installed to a test device from play store.
However, in any other device that installed the app from the Play Store, ads are not shown and LOAD_FAIL event fires with error code: 3 and reason: No fill.
My admob profile is complete. (I have an older app with working ads)
I have the <variable name="PLAY_SERVICES_VERSION" value="11.0.0" /> dependency in the config.xml file. (I also tried the version 17.0.0)
I created app-ads.txt in my developer website
I tried to create new ad units and use them
I didn't try to remove the app from the store and create another one as it takes too long to be confirmed.
I couldn't get any reply from the Admob support or github repo. I appreciate any help. Thanks.
Since the ads was working when installed from apk, I thought the case is different from newly published apps. However, it just begin to work after 8-10 days from publication. As the other "no fill" error cases, the solution was just waiting.
I have uploaded an app the play console and it is now on the Play Store but says (Beta). I was just wondering how do I publish the full version?
You promote the Production Track. Please note that if you are enrolled on a testing track you will still see Beta next to your app name, however if you use another Google Account that is not enrolled, you should not see Beta.
Why am i getting "failed to flash file gapps-jb-20130813-signed.zip genymotion" this error when i am trying to install Google apps on Genymotion simulator.
I just drag n dropped >>gapps-jb-20130813-signed.zip<< and gave this error.
Please let me know if anyone else has faced the same issue and the fix.
I also faced same issue I sort it by downloading the correct GApps meant for particular android version.Here is the list:
Google Apps for Android 6.0
1) (https://www.androidfilehost.com/?fid=96042739161891406 -
gapps-L-4-21-15.zip)
2) (https://www.androidfilehost.com/?fid=24052804347835438 -
benzo-gapps-M-20151011-signed-chroma-r3.zip)
Google Apps for Android 5.1
(https://www.androidfilehost.com/?fid=96042739161891406 -
gapps-L-4-21-15.zip)
Google Apps for Android 5.0
(https://www.androidfilehost.com/?fid=95784891001614559 -
gapps-lp-20141109-signed.zip)
Google Apps for Android 4.4.4
(https://www.androidfilehost.com/?fid=23501681358544845 -
gapps-kk-20140606-signed.zip)
Google Apps for Android 4.3
(https://www.androidfilehost.com/?fid=23060877490000124 -
gapps-jb-20130813-signed.zip)
Google Apps for Android 4.2
(https://www.androidfilehost.com/?fid=23060877490000128 -
gapps-jb-20130812-signed.zip)
Google Apps for Android 4.1
(https://www.androidfilehost.com/?fid=22979706399755082 -
gapps-jb-20121011-signed.zip)
Google Apps for Android 2.3.7
(http://www.mediafire.com/download/bs063kb0m742o5l/gapps-gb-20131027-signed.zip- gapps-gb-20131027-signe.zip)
Note: For Android 6.0 ,you need to flash first .zip i.e(gapps-L-4-21-15.zip)and reboot .Then you need to sign-in to your google account and then flash second .zip (benzo-gapps-M-20151011-signed-chroma-r3.zip.) and reboot again.
Hope it helps ...Cheers
Feb-2016
Download and install GAPPS APK from the official website.
Grant root permissions to the app and click next
This app will automatically detect CPU Architecture and Android version. please note it down
Then go to OPEN GAPPS WEBSITE
And then select desired Platform , Android version and Variant and click download button.
After downloading Gapps.zip file. Now Drag and Drop GApps.zip , Genymotion-ARM-Translation one by one then restart Genymotion.
Completely remove your Virtualbox and Genymotion. There are old registry files hidden in your computer which are preventing you from flashing Gapp properly.
Here are few links teaching you how to uninstall Genymotion and Virtualbox:
uninstall-genymotion-genymotion-removal-genymotion-windows-uninstaller
Don't download their software because it doesn't remove everything
how-to-uninstall-virtualbox-drivers-on-windows
And finally there should be a Genymobile folder in your
User -> (Username) -> AppData -> Local folder
Hope that helped
This issues is faced while you put this file in something wrong version of genymotion devices.
here you can get proper guide line for installing the gapps files in genymotion device,
it will be a different for all the version.so might be your file would not suitable for your version, so please follow the guideline
That'll happen when you're trying to install flashable gapps meant for a different api version. Make sure the device you're emulating in genymotion is the version the gapps is meant for.
Follow this guide: http://inthecheesefactory.com/blog/how-to-install-google-services-on-genymotion/en
After upgrading my iPhone 5 to iOS 7 beta, it seems I have to re-connect it to Testflight.
Unfortunately, I can't install the provisioning profile:
After selecting 'Reconnect Device', 'Install Profile', 'Install Now', the alert is 'Profile Installation Failed. You iPhone is not activated'
I tried to remove the previous profiles, clear Safari cache and reboot, but no success...
Short answer - Go to TestFlight directly on Mobile Safari and use the TestFlight CocoaPod.
We got TestFlight working on the latest iOS 7 build. The TestFlight "app" that installs doesn't work, but manually visiting the TestFlight site in Mobile Safari allows you to install the profile and load the app. Nothing special needed. It sometimes takes a few tries loading the profile to get it to actually load.
Also, loading our apps into TestFlight wasn't working, so we started using the TestFlight CocoaPod and it works great.
I got it working on an iPad mini running iOS 7 beta 5, that was previously used with testflight while running iOS 6. It seems that it will work under some circumstances. What I did:
Unregistered the device from its connected testflight user account (actually this step might be irrelevant)
Launched testflightapp.com from Safari, not from any icon placed on home screen. It has to be from Safari where the url bar is shown. From here I could install betas. However the device itself is not listed under any user and it is not activated. While trying to activate it, testflight app says the registering works OK, however it really fails.
So, it MIGHT work but it's clear that the people at testflight has some work to do.
More: I am unable to get it working with an iPhone 4 iOS 7 beta 5 at all. The iPhone has not previously been used with testflight and seems to require an activation through that profile (at testflight or Apple, not sure) but the activation fails and there's no app list coming up in Safari, just the activation sequence. The key here might be that the device must have been used with testflight before, while on iOS previous to 7.
It seems that using testflight with iOS 7 beta does not work and/or is not supported at the moment.
Not sure what happened here but I was using testflight with an iPad mini that had iOS6. When I just upgraded it to iOS 7, the testflight site loads on the device, however installs never process.
I found the answer of Lysann Schlegel most useful. After some experimenting, I found out that simply opening TestFlight from Safari works fine. Don't use TestFlight app icon.
I had the same problem. In my case after i connect my iphone with the xcode/ organizer beta it let me install again the apps.
Check in Settings if you have the Developer options.
I'm sorry to say that this is currently untested and is a only workaround, but try downloading the ipa file from the TestFlightApp "Share this build" link and use xcode to install it.
This link is normally provided to allow pre iOS4 users to install using testflightapp.com
Even if this works this workaround is probably unacceptable for a vast majority of beta testers.
I'd say also use the "iphone configuration utility" but I suspect that the current release does not support the iOS beta.
If this does fix the issue for people then it's some confirmation that it's mainly the OTA profile that's at issue.
I did a fresh install of iOS 7 beta 6 (it did not have any provisioning profiles before) and was able to load an app from TestFlight. Installing the provisioning profile failed from the web, but I was able to get the correct one onto the device through XCode's Organizer. Then I downloaded the app from TestFlight in Safari (not the little portal TestFlight app). It loaded up just fine.