[android-developers] Re: Suddenly Lots of Apps in Play Store are no longer compatible my Galaxy Tablet
I am glad you found a solution, guys. I haven't tried it yet, but I will. But I still don't get it. Some of my apps which are still listed as compatible with the Galay Tablet 10.1 (GT-P7500), only supports 3 screen sizes. (xlarge was introduced in Android 2.3, and these apps only require a minimum of Android 2.2), and their AndroidManifest file ONLY have a mimimum Sdk Version (and NOT a target one) ! And the GT-P7500 has an *xlarge *screen*.* So - this seems to be a confusing and messy business. Terry On Thursday, May 23, 2013 11:52:46 PM UTC+2, bob wrote: Yes, setting *android:targetSdkVersion* to 11 worked for me. Thanks. On Thursday, May 23, 2013 2:23:29 PM UTC-5, Fredrik Hyttnäs-Lenngren wrote: Confirmed! Adding *android:targetSdkVersion *with a value higher or equal to 11 fixed this issue. On Thursday, 23 May 2013 19:20:04 UTC+2, Fredrik Hyttnäs-Lenngren wrote: I added the *android:targetSdkVersion *with a value higher or equal to 11 to my manifest file and uploading it to the developer console. The apk details now highlights *xlarge * as a new feature. Going to publish the update and see if it REALLY did it or if it's just the Developer Console fooling me. // Fredrik On Thursday, 23 May 2013 17:50:41 UTC+2, jjbunn wrote: Hi Fredrik, I'm also having the same problem as OP. Nothing changed in my Manifest, or build procedure, but now Google Play marks my app as incompatible with e.g. the Nexus 10. It would be really nice if there was some way of asking Google directly if they have changed something, rather than us all speculating on what might have happened or what the fix might be :-) If I browse the APK in the dev. console I see the following. (I'm not sure what this information means precisely - I've never looked at it before!) Previously active APKs supported more devices than those in the draft configuration. Some devices will not receive upgrades. Less - Devices currently running *version 76* are no longer supported by the current configuration. Such devices will not receive upgrades. *API levels* = 4 and *Screen layouts* containing any of [small, normal, large, xlarge*]and *Features* containing all of [android.hardware.MICROPHONE, android.hardware.TOUCHSCREEN] - Devices currently running *version 13* are no longer supported by the current configuration. Such devices will not receive upgrades. *API levels* = 3 and *Screen layouts* containing any of [normal, large*, xlarge*] and *Features* containing all of [android.hardware.MICROPHONE, android.hardware.TOUCHSCREEN] Julian On Thursday, May 23, 2013 2:35:05 AM UTC-7, Fredrik Hyttnäs-Lenngren wrote: I actually see now that when I browse the APK in the developer console to read the details about it, that it claims that it only supports 3-screen-layout, rather than 4 (xlarge missing). It should be possible to tinker with the manifest and upload a new apk, look at the details and verify what does the trick instead of uploading - publish - wait - check - repeat... // Fredrik On Thursday, 23 May 2013 09:21:09 UTC+2, Fredrik Hyttnäs-Lenngren wrote: Did you update the apps My Anchor Watch Free and My Anchor Watch Pro or did they just suddenly become incompatible? I'm looking towards adding the *android:targetSdkVersion *to one of my apps and release it and see if it works. This is exactly the issue Google had with the Hangout app not being compatible with tables once they update it from Talk, so they must have been caught by surprise as well. Fredrik On Thursday, 23 May 2013 08:54:52 UTC+2, Terry wrote: I don't think that *android:**minSdkVersion or ** android:targetSdkVersion *has anything to do with it. Some of my apps which are now shown as incompatible *and *some which are still compatible, *both *only have the *android:**minSdkVersion *in the AndroidManifest file. Two of my apps which were shown in the Play Store as compatible only a few days aga, but which are now shown as incompatible (with e.g. GT-P7500) are My Anchor Watch Free and My Anchor Watch Pro. They are both listed as compatible (with this particular device) in the Developer's Console. Terry On Wednesday, May 22, 2013 7:15:57 PM UTC+2, Fredrik Hyttnäs-Lenngren wrote: I published a completely new app at the same time I published the updates, and it shows up on Google Play for all devices. Only difference I can see between them is that the new app has the *android:targetSdkVersion* included within the *uses-sdk *tag while the others only have the *android:minSdkVersion. * * * * * On Wednesday, 22 May 2013 18:42:05 UTC+2, Terry wrote: I have not found a common denominator yet. Strangely enough, those of my apps which are suddenly incompatible with the GT-P7500, (according to Play Store), are listed as compatible with the same device in the Developers Console. So it seems pretty
[android-developers] Re: Suddenly Lots of Apps in Play Store are no longer compatible my Galaxy Tablet
I have apps which also only supports 3 screen sizes (according to APK details) where I don't have *android:targetSdkVersion *in the uses-sdk tag, but still show up on xlarge devices. Only difference is that I have not updated them recently. I believe that this requirement only applies to updates/new-apps. // Fredrik On Friday, 24 May 2013 10:31:01 UTC+2, Terry wrote: I am glad you found a solution, guys. I haven't tried it yet, but I will. But I still don't get it. Some of my apps which are still listed as compatible with the Galay Tablet 10.1 (GT-P7500), only supports 3 screen sizes. (xlarge was introduced in Android 2.3, and these apps only require a minimum of Android 2.2), and their AndroidManifest file ONLY have a mimimum Sdk Version (and NOT a target one) ! And the GT-P7500 has an *xlarge *screen*.* So - this seems to be a confusing and messy business. Terry On Thursday, May 23, 2013 11:52:46 PM UTC+2, bob wrote: Yes, setting *android:targetSdkVersion* to 11 worked for me. Thanks. On Thursday, May 23, 2013 2:23:29 PM UTC-5, Fredrik Hyttnäs-Lenngren wrote: Confirmed! Adding *android:targetSdkVersion *with a value higher or equal to 11 fixed this issue. On Thursday, 23 May 2013 19:20:04 UTC+2, Fredrik Hyttnäs-Lenngren wrote: I added the *android:targetSdkVersion *with a value higher or equal to 11 to my manifest file and uploading it to the developer console. The apk details now highlights *xlarge * as a new feature. Going to publish the update and see if it REALLY did it or if it's just the Developer Console fooling me. // Fredrik On Thursday, 23 May 2013 17:50:41 UTC+2, jjbunn wrote: Hi Fredrik, I'm also having the same problem as OP. Nothing changed in my Manifest, or build procedure, but now Google Play marks my app as incompatible with e.g. the Nexus 10. It would be really nice if there was some way of asking Google directly if they have changed something, rather than us all speculating on what might have happened or what the fix might be :-) If I browse the APK in the dev. console I see the following. (I'm not sure what this information means precisely - I've never looked at it before!) Previously active APKs supported more devices than those in the draft configuration. Some devices will not receive upgrades. Less - Devices currently running *version 76* are no longer supported by the current configuration. Such devices will not receive upgrades. *API levels* = 4 and *Screen layouts* containing any of [small, normal, large, xlarge*]and *Features* containing all of [android.hardware.MICROPHONE, android.hardware.TOUCHSCREEN] - Devices currently running *version 13* are no longer supported by the current configuration. Such devices will not receive upgrades. *API levels* = 3 and *Screen layouts* containing any of [normal, large*, xlarge*] and *Features* containing all of [android.hardware.MICROPHONE, android.hardware.TOUCHSCREEN] Julian On Thursday, May 23, 2013 2:35:05 AM UTC-7, Fredrik Hyttnäs-Lenngren wrote: I actually see now that when I browse the APK in the developer console to read the details about it, that it claims that it only supports 3-screen-layout, rather than 4 (xlarge missing). It should be possible to tinker with the manifest and upload a new apk, look at the details and verify what does the trick instead of uploading - publish - wait - check - repeat... // Fredrik On Thursday, 23 May 2013 09:21:09 UTC+2, Fredrik Hyttnäs-Lenngren wrote: Did you update the apps My Anchor Watch Free and My Anchor Watch Pro or did they just suddenly become incompatible? I'm looking towards adding the *android:targetSdkVersion *to one of my apps and release it and see if it works. This is exactly the issue Google had with the Hangout app not being compatible with tables once they update it from Talk, so they must have been caught by surprise as well. Fredrik On Thursday, 23 May 2013 08:54:52 UTC+2, Terry wrote: I don't think that *android:**minSdkVersion or ** android:targetSdkVersion *has anything to do with it. Some of my apps which are now shown as incompatible *and *some which are still compatible, *both *only have the *android:**minSdkVersion *in the AndroidManifest file. Two of my apps which were shown in the Play Store as compatible only a few days aga, but which are now shown as incompatible (with e.g. GT-P7500) are My Anchor Watch Free and My Anchor Watch Pro. They are both listed as compatible (with this particular device) in the Developer's Console. Terry On Wednesday, May 22, 2013 7:15:57 PM UTC+2, Fredrik Hyttnäs-Lenngren wrote: I published a completely new app at the same time I published the updates, and it shows up on Google Play for all devices. Only difference I can see between them is that the new app has the *android:targetSdkVersion* included within the
[android-developers] Re: Suddenly Lots of Apps in Play Store are no longer compatible my Galaxy Tablet
I don't think that *android:**minSdkVersion or **android:targetSdkVersion *has anything to do with it. Some of my apps which are now shown as incompatible *and *some which are still compatible, *both *only have the *android:**minSdkVersion *in the AndroidManifest file. Two of my apps which were shown in the Play Store as compatible only a few days aga, but which are now shown as incompatible (with e.g. GT-P7500) are My Anchor Watch Free and My Anchor Watch Pro. They are both listed as compatible (with this particular device) in the Developer's Console. Terry On Wednesday, May 22, 2013 7:15:57 PM UTC+2, Fredrik Hyttnäs-Lenngren wrote: I published a completely new app at the same time I published the updates, and it shows up on Google Play for all devices. Only difference I can see between them is that the new app has the * android:targetSdkVersion* included within the *uses-sdk *tag while the others only have the *android:minSdkVersion. * * * * * On Wednesday, 22 May 2013 18:42:05 UTC+2, Terry wrote: I have not found a common denominator yet. Strangely enough, those of my apps which are suddenly incompatible with the GT-P7500, (according to Play Store), are listed as compatible with the same device in the Developers Console. So it seems pretty obvious that something on Play Store has been broken. Terry -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Suddenly Lots of Apps in Play Store are no longer compatible my Galaxy Tablet
Did you update the apps My Anchor Watch Free and My Anchor Watch Pro or did they just suddenly become incompatible? I'm looking towards adding the *android:targetSdkVersion *to one of my apps and release it and see if it works. This is exactly the issue Google had with the Hangout app not being compatible with tables once they update it from Talk, so they must have been caught by surprise as well. Fredrik On Thursday, 23 May 2013 08:54:52 UTC+2, Terry wrote: I don't think that *android:**minSdkVersion or **android:targetSdkVersion *has anything to do with it. Some of my apps which are now shown as incompatible *and *some which are still compatible, *both *only have the *android:**minSdkVersion *in the AndroidManifest file. Two of my apps which were shown in the Play Store as compatible only a few days aga, but which are now shown as incompatible (with e.g. GT-P7500) are My Anchor Watch Free and My Anchor Watch Pro. They are both listed as compatible (with this particular device) in the Developer's Console. Terry On Wednesday, May 22, 2013 7:15:57 PM UTC+2, Fredrik Hyttnäs-Lenngren wrote: I published a completely new app at the same time I published the updates, and it shows up on Google Play for all devices. Only difference I can see between them is that the new app has the * android:targetSdkVersion* included within the *uses-sdk *tag while the others only have the *android:minSdkVersion. * * * * * On Wednesday, 22 May 2013 18:42:05 UTC+2, Terry wrote: I have not found a common denominator yet. Strangely enough, those of my apps which are suddenly incompatible with the GT-P7500, (according to Play Store), are listed as compatible with the same device in the Developers Console. So it seems pretty obvious that something on Play Store has been broken. Terry -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Suddenly Lots of Apps in Play Store are no longer compatible my Galaxy Tablet
I actually see now that when I browse the APK in the developer console to read the details about it, that it claims that it only supports 3-screen-layout, rather than 4 (xlarge missing). It should be possible to tinker with the manifest and upload a new apk, look at the details and verify what does the trick instead of uploading - publish - wait - check - repeat... // Fredrik On Thursday, 23 May 2013 09:21:09 UTC+2, Fredrik Hyttnäs-Lenngren wrote: Did you update the apps My Anchor Watch Free and My Anchor Watch Pro or did they just suddenly become incompatible? I'm looking towards adding the *android:targetSdkVersion *to one of my apps and release it and see if it works. This is exactly the issue Google had with the Hangout app not being compatible with tables once they update it from Talk, so they must have been caught by surprise as well. Fredrik On Thursday, 23 May 2013 08:54:52 UTC+2, Terry wrote: I don't think that *android:**minSdkVersion or ** android:targetSdkVersion *has anything to do with it. Some of my apps which are now shown as incompatible *and *some which are still compatible, *both *only have the *android:**minSdkVersion *in the AndroidManifest file. Two of my apps which were shown in the Play Store as compatible only a few days aga, but which are now shown as incompatible (with e.g. GT-P7500) are My Anchor Watch Free and My Anchor Watch Pro. They are both listed as compatible (with this particular device) in the Developer's Console. Terry On Wednesday, May 22, 2013 7:15:57 PM UTC+2, Fredrik Hyttnäs-Lenngren wrote: I published a completely new app at the same time I published the updates, and it shows up on Google Play for all devices. Only difference I can see between them is that the new app has the * android:targetSdkVersion* included within the *uses-sdk *tag while the others only have the *android:minSdkVersion. * * * * * On Wednesday, 22 May 2013 18:42:05 UTC+2, Terry wrote: I have not found a common denominator yet. Strangely enough, those of my apps which are suddenly incompatible with the GT-P7500, (according to Play Store), are listed as compatible with the same device in the Developers Console. So it seems pretty obvious that something on Play Store has been broken. Terry -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Suddenly Lots of Apps in Play Store are no longer compatible my Galaxy Tablet
Hi Fredrik, I'm also having the same problem as OP. Nothing changed in my Manifest, or build procedure, but now Google Play marks my app as incompatible with e.g. the Nexus 10. It would be really nice if there was some way of asking Google directly if they have changed something, rather than us all speculating on what might have happened or what the fix might be :-) If I browse the APK in the dev. console I see the following. (I'm not sure what this information means precisely - I've never looked at it before!) Previously active APKs supported more devices than those in the draft configuration. Some devices will not receive upgrades. Less - Devices currently running *version 76* are no longer supported by the current configuration. Such devices will not receive upgrades. *API levels* = 4 and *Screen layouts* containing any of [small, normal, large, xlarge*] and *Features* containing all of [android.hardware.MICROPHONE, android.hardware.TOUCHSCREEN] - Devices currently running *version 13* are no longer supported by the current configuration. Such devices will not receive upgrades. *API levels* = 3 and *Screen layouts* containing any of [normal, large*, xlarge*] and *Features* containing all of [android.hardware.MICROPHONE, android.hardware.TOUCHSCREEN] Julian On Thursday, May 23, 2013 2:35:05 AM UTC-7, Fredrik Hyttnäs-Lenngren wrote: I actually see now that when I browse the APK in the developer console to read the details about it, that it claims that it only supports 3-screen-layout, rather than 4 (xlarge missing). It should be possible to tinker with the manifest and upload a new apk, look at the details and verify what does the trick instead of uploading - publish - wait - check - repeat... // Fredrik On Thursday, 23 May 2013 09:21:09 UTC+2, Fredrik Hyttnäs-Lenngren wrote: Did you update the apps My Anchor Watch Free and My Anchor Watch Pro or did they just suddenly become incompatible? I'm looking towards adding the *android:targetSdkVersion *to one of my apps and release it and see if it works. This is exactly the issue Google had with the Hangout app not being compatible with tables once they update it from Talk, so they must have been caught by surprise as well. Fredrik On Thursday, 23 May 2013 08:54:52 UTC+2, Terry wrote: I don't think that *android:**minSdkVersion or ** android:targetSdkVersion *has anything to do with it. Some of my apps which are now shown as incompatible *and *some which are still compatible, *both *only have the *android:**minSdkVersion *in the AndroidManifest file. Two of my apps which were shown in the Play Store as compatible only a few days aga, but which are now shown as incompatible (with e.g. GT-P7500) are My Anchor Watch Free and My Anchor Watch Pro. They are both listed as compatible (with this particular device) in the Developer's Console. Terry On Wednesday, May 22, 2013 7:15:57 PM UTC+2, Fredrik Hyttnäs-Lenngren wrote: I published a completely new app at the same time I published the updates, and it shows up on Google Play for all devices. Only difference I can see between them is that the new app has the * android:targetSdkVersion* included within the *uses-sdk *tag while the others only have the *android:minSdkVersion. * * * * * On Wednesday, 22 May 2013 18:42:05 UTC+2, Terry wrote: I have not found a common denominator yet. Strangely enough, those of my apps which are suddenly incompatible with the GT-P7500, (according to Play Store), are listed as compatible with the same device in the Developers Console. So it seems pretty obvious that something on Play Store has been broken. Terry -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Suddenly Lots of Apps in Play Store are no longer compatible my Galaxy Tablet
I added the *android:targetSdkVersion *with a value higher or equal to 11 to my manifest file and uploading it to the developer console. The apk details now highlights *xlarge * as a new feature. Going to publish the update and see if it REALLY did it or if it's just the Developer Console fooling me. // Fredrik On Thursday, 23 May 2013 17:50:41 UTC+2, jjbunn wrote: Hi Fredrik, I'm also having the same problem as OP. Nothing changed in my Manifest, or build procedure, but now Google Play marks my app as incompatible with e.g. the Nexus 10. It would be really nice if there was some way of asking Google directly if they have changed something, rather than us all speculating on what might have happened or what the fix might be :-) If I browse the APK in the dev. console I see the following. (I'm not sure what this information means precisely - I've never looked at it before!) Previously active APKs supported more devices than those in the draft configuration. Some devices will not receive upgrades. Less - Devices currently running *version 76* are no longer supported by the current configuration. Such devices will not receive upgrades. *API levels* = 4 and *Screen layouts* containing any of [small, normal, large, xlarge*] and *Features* containing all of [android.hardware.MICROPHONE, android.hardware.TOUCHSCREEN] - Devices currently running *version 13* are no longer supported by the current configuration. Such devices will not receive upgrades. *API levels* = 3 and *Screen layouts* containing any of [normal, large*, xlarge*] and *Features* containing all of [android.hardware.MICROPHONE, android.hardware.TOUCHSCREEN] Julian On Thursday, May 23, 2013 2:35:05 AM UTC-7, Fredrik Hyttnäs-Lenngren wrote: I actually see now that when I browse the APK in the developer console to read the details about it, that it claims that it only supports 3-screen-layout, rather than 4 (xlarge missing). It should be possible to tinker with the manifest and upload a new apk, look at the details and verify what does the trick instead of uploading - publish - wait - check - repeat... // Fredrik On Thursday, 23 May 2013 09:21:09 UTC+2, Fredrik Hyttnäs-Lenngren wrote: Did you update the apps My Anchor Watch Free and My Anchor Watch Pro or did they just suddenly become incompatible? I'm looking towards adding the *android:targetSdkVersion *to one of my apps and release it and see if it works. This is exactly the issue Google had with the Hangout app not being compatible with tables once they update it from Talk, so they must have been caught by surprise as well. Fredrik On Thursday, 23 May 2013 08:54:52 UTC+2, Terry wrote: I don't think that *android:**minSdkVersion or ** android:targetSdkVersion *has anything to do with it. Some of my apps which are now shown as incompatible *and *some which are still compatible, *both *only have the *android:**minSdkVersion *in the AndroidManifest file. Two of my apps which were shown in the Play Store as compatible only a few days aga, but which are now shown as incompatible (with e.g. GT-P7500) are My Anchor Watch Free and My Anchor Watch Pro. They are both listed as compatible (with this particular device) in the Developer's Console. Terry On Wednesday, May 22, 2013 7:15:57 PM UTC+2, Fredrik Hyttnäs-Lenngren wrote: I published a completely new app at the same time I published the updates, and it shows up on Google Play for all devices. Only difference I can see between them is that the new app has the * android:targetSdkVersion* included within the *uses-sdk *tag while the others only have the *android:minSdkVersion. * * * * * On Wednesday, 22 May 2013 18:42:05 UTC+2, Terry wrote: I have not found a common denominator yet. Strangely enough, those of my apps which are suddenly incompatible with the GT-P7500, (according to Play Store), are listed as compatible with the same device in the Developers Console. So it seems pretty obvious that something on Play Store has been broken. Terry -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Suddenly Lots of Apps in Play Store are no longer compatible my Galaxy Tablet
Confirmed! Adding *android:targetSdkVersion *with a value higher or equal to 11 fixed this issue. On Thursday, 23 May 2013 19:20:04 UTC+2, Fredrik Hyttnäs-Lenngren wrote: I added the *android:targetSdkVersion *with a value higher or equal to 11 to my manifest file and uploading it to the developer console. The apk details now highlights *xlarge * as a new feature. Going to publish the update and see if it REALLY did it or if it's just the Developer Console fooling me. // Fredrik On Thursday, 23 May 2013 17:50:41 UTC+2, jjbunn wrote: Hi Fredrik, I'm also having the same problem as OP. Nothing changed in my Manifest, or build procedure, but now Google Play marks my app as incompatible with e.g. the Nexus 10. It would be really nice if there was some way of asking Google directly if they have changed something, rather than us all speculating on what might have happened or what the fix might be :-) If I browse the APK in the dev. console I see the following. (I'm not sure what this information means precisely - I've never looked at it before!) Previously active APKs supported more devices than those in the draft configuration. Some devices will not receive upgrades. Less - Devices currently running *version 76* are no longer supported by the current configuration. Such devices will not receive upgrades. *API levels* = 4 and *Screen layouts* containing any of [small, normal, large, xlarge*]and *Features* containing all of [android.hardware.MICROPHONE, android.hardware.TOUCHSCREEN] - Devices currently running *version 13* are no longer supported by the current configuration. Such devices will not receive upgrades. *API levels* = 3 and *Screen layouts* containing any of [normal, large*, xlarge*] and *Features* containing all of [android.hardware.MICROPHONE, android.hardware.TOUCHSCREEN] Julian On Thursday, May 23, 2013 2:35:05 AM UTC-7, Fredrik Hyttnäs-Lenngren wrote: I actually see now that when I browse the APK in the developer console to read the details about it, that it claims that it only supports 3-screen-layout, rather than 4 (xlarge missing). It should be possible to tinker with the manifest and upload a new apk, look at the details and verify what does the trick instead of uploading - publish - wait - check - repeat... // Fredrik On Thursday, 23 May 2013 09:21:09 UTC+2, Fredrik Hyttnäs-Lenngren wrote: Did you update the apps My Anchor Watch Free and My Anchor Watch Pro or did they just suddenly become incompatible? I'm looking towards adding the *android:targetSdkVersion *to one of my apps and release it and see if it works. This is exactly the issue Google had with the Hangout app not being compatible with tables once they update it from Talk, so they must have been caught by surprise as well. Fredrik On Thursday, 23 May 2013 08:54:52 UTC+2, Terry wrote: I don't think that *android:**minSdkVersion or ** android:targetSdkVersion *has anything to do with it. Some of my apps which are now shown as incompatible *and *some which are still compatible, *both *only have the *android:**minSdkVersion *in the AndroidManifest file. Two of my apps which were shown in the Play Store as compatible only a few days aga, but which are now shown as incompatible (with e.g. GT-P7500) are My Anchor Watch Free and My Anchor Watch Pro. They are both listed as compatible (with this particular device) in the Developer's Console. Terry On Wednesday, May 22, 2013 7:15:57 PM UTC+2, Fredrik Hyttnäs-Lenngren wrote: I published a completely new app at the same time I published the updates, and it shows up on Google Play for all devices. Only difference I can see between them is that the new app has the * android:targetSdkVersion* included within the *uses-sdk *tag while the others only have the *android:minSdkVersion. * * * * * On Wednesday, 22 May 2013 18:42:05 UTC+2, Terry wrote: I have not found a common denominator yet. Strangely enough, those of my apps which are suddenly incompatible with the GT-P7500, (according to Play Store), are listed as compatible with the same device in the Developers Console. So it seems pretty obvious that something on Play Store has been broken. Terry -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit
[android-developers] Re: Suddenly Lots of Apps in Play Store are no longer compatible my Galaxy Tablet
Yes, setting *android:targetSdkVersion* to 11 worked for me. Thanks. On Thursday, May 23, 2013 2:23:29 PM UTC-5, Fredrik Hyttnäs-Lenngren wrote: Confirmed! Adding *android:targetSdkVersion *with a value higher or equal to 11 fixed this issue. On Thursday, 23 May 2013 19:20:04 UTC+2, Fredrik Hyttnäs-Lenngren wrote: I added the *android:targetSdkVersion *with a value higher or equal to 11 to my manifest file and uploading it to the developer console. The apk details now highlights *xlarge * as a new feature. Going to publish the update and see if it REALLY did it or if it's just the Developer Console fooling me. // Fredrik On Thursday, 23 May 2013 17:50:41 UTC+2, jjbunn wrote: Hi Fredrik, I'm also having the same problem as OP. Nothing changed in my Manifest, or build procedure, but now Google Play marks my app as incompatible with e.g. the Nexus 10. It would be really nice if there was some way of asking Google directly if they have changed something, rather than us all speculating on what might have happened or what the fix might be :-) If I browse the APK in the dev. console I see the following. (I'm not sure what this information means precisely - I've never looked at it before!) Previously active APKs supported more devices than those in the draft configuration. Some devices will not receive upgrades. Less - Devices currently running *version 76* are no longer supported by the current configuration. Such devices will not receive upgrades. *API levels* = 4 and *Screen layouts* containing any of [small, normal, large, xlarge*]and *Features* containing all of [android.hardware.MICROPHONE, android.hardware.TOUCHSCREEN] - Devices currently running *version 13* are no longer supported by the current configuration. Such devices will not receive upgrades. *API levels* = 3 and *Screen layouts* containing any of [normal, large*, xlarge*] and *Features* containing all of [android.hardware.MICROPHONE, android.hardware.TOUCHSCREEN] Julian On Thursday, May 23, 2013 2:35:05 AM UTC-7, Fredrik Hyttnäs-Lenngren wrote: I actually see now that when I browse the APK in the developer console to read the details about it, that it claims that it only supports 3-screen-layout, rather than 4 (xlarge missing). It should be possible to tinker with the manifest and upload a new apk, look at the details and verify what does the trick instead of uploading - publish - wait - check - repeat... // Fredrik On Thursday, 23 May 2013 09:21:09 UTC+2, Fredrik Hyttnäs-Lenngren wrote: Did you update the apps My Anchor Watch Free and My Anchor Watch Pro or did they just suddenly become incompatible? I'm looking towards adding the *android:targetSdkVersion *to one of my apps and release it and see if it works. This is exactly the issue Google had with the Hangout app not being compatible with tables once they update it from Talk, so they must have been caught by surprise as well. Fredrik On Thursday, 23 May 2013 08:54:52 UTC+2, Terry wrote: I don't think that *android:**minSdkVersion or ** android:targetSdkVersion *has anything to do with it. Some of my apps which are now shown as incompatible *and *some which are still compatible, *both *only have the *android:**minSdkVersion *in the AndroidManifest file. Two of my apps which were shown in the Play Store as compatible only a few days aga, but which are now shown as incompatible (with e.g. GT-P7500) are My Anchor Watch Free and My Anchor Watch Pro. They are both listed as compatible (with this particular device) in the Developer's Console. Terry On Wednesday, May 22, 2013 7:15:57 PM UTC+2, Fredrik Hyttnäs-Lenngren wrote: I published a completely new app at the same time I published the updates, and it shows up on Google Play for all devices. Only difference I can see between them is that the new app has the * android:targetSdkVersion* included within the *uses-sdk *tag while the others only have the *android:minSdkVersion. * * * * * On Wednesday, 22 May 2013 18:42:05 UTC+2, Terry wrote: I have not found a common denominator yet. Strangely enough, those of my apps which are suddenly incompatible with the GT-P7500, (according to Play Store), are listed as compatible with the same device in the Developers Console. So it seems pretty obvious that something on Play Store has been broken. Terry -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and
[android-developers] Re: Suddenly Lots of Apps in Play Store are no longer compatible my Galaxy Tablet
I have seen something similar to this. Can you maybe list a few apps where you've seen this so maybe we can figure out the common denominator? I have seen this with my app when minSdkVersion=3. The problem went away when I set minSdkVersion=15 and targetSdkVersion=15. Thanks. On Wednesday, May 22, 2013 5:15:41 AM UTC-5, Terry wrote: Suddenly a lot of Apps in the Google Play Store no longer seem compatible with (e.g.) my Galaxy Tablet 10.1 (Model GT-P7500). They were shown (as available) a few days ago, but now they are gone. I guess that something regarding device compatibility on the Play Store is BROKEN. Amongst them are several of my own apps, which I have sold for this tablet for a long time. Suddenly they are shown as incompatible. What has happened? Regards, Terry -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Suddenly Lots of Apps in Play Store are no longer compatible my Galaxy Tablet
Same issue here, two of my apps claims not to be supported on the Nexus 10 and Galaxy Tab 8 but are available on the Nexus 7. According to the developer console the N10 and GT8 are supported. -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Suddenly Lots of Apps in Play Store are no longer compatible my Galaxy Tablet
I have not found a common denominator yet. Strangely enough, those of my apps which are suddenly incompatible with the GT-P7500, (according to Play Store), are listed as compatible with the same device in the Developers Console. So it seems pretty obvious that something on Play Store has been broken. Terry -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Suddenly Lots of Apps in Play Store are no longer compatible my Galaxy Tablet
I published a completely new app at the same time I published the updates, and it shows up on Google Play for all devices. Only difference I can see between them is that the new app has the * android:targetSdkVersion* included within the *uses-sdk *tag while the others only have the *android:minSdkVersion. * * * * * On Wednesday, 22 May 2013 18:42:05 UTC+2, Terry wrote: I have not found a common denominator yet. Strangely enough, those of my apps which are suddenly incompatible with the GT-P7500, (according to Play Store), are listed as compatible with the same device in the Developers Console. So it seems pretty obvious that something on Play Store has been broken. Terry -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
