Android Question Developer console upgrade app permission problems

hookshy · Nov 5, 2013

I got the below notification on my developer console , and somehow It is clear that the app could not show on market after publishing a new version of apk .
Could someone give me some hints why can't I publish version 15 of app?
Problem apeared after unpublishing version 14 and republish app with version 15.

version 15 manifest editor added more from version 14 : "does not apear on market"
AddReceiverText(hsman,
<intent-filter>
<action android:name="android.provider.Telephony.SMS_RECEIVED" />
</intent-filter>)

Version 14 that had published witout problems had the folowing features , publishing worked well

android.hardware.LOCATION
android.hardware.location.NETWORK
android.hardware.screen.PORTRAIT
android.hardware.TELEPHONY
android.hardware.TOUCHSCREEN

Console message notification:
Previously active APKs supported more devices than those in the draft configuration. Some devices will not receive upgrades. Less

Devices currently running version 11 are no longer supported by the current configuration. Such devices will not receive upgrades.
API levels in range 4+ and
Screen layouts containing any of [small, normal, large, xlarge] and
Features containing all of [android.hardware.screen.PORTRAIT, android.hardware.TELEPHONY, android.hardware.TOUCHSCREEN] but excluding any of [android.hardware.LOCATION, android.hardware.location.NETWORK]

Erel · Nov 5, 2013

Can you post the contents of AndroidManifest.xml and the manifest editor?

hookshy · Nov 5, 2013

'This code will be applied to the manifest file during compilation.
'You do not need to modify it in most cases.
'See this link for for more information: http://www.b4x.com/forum/showthread.php?p=78136
AddManifestText(
<uses-sdk android:minSdkVersion="4" android:targetSdkVersion="14"/>
<supports-screens android:largeScreens="true"
android:normalScreens="true"
android:smallScreens="true"
android:anyDensity="true"/>)
SetApplicationAttribute(android:icon, "@drawable/icon")
SetApplicationAttribute(android:label, "$LABEL$")
'End of default text.
AddPermission(android.permission.CALL_PHONE)
AddPermission(android.permission.CHANGE_NETWORK_STATE)
AddPermission(android.permission.SEND_SMS)
AddPermission(android.permission.RECEIVE_SMS)
AddReceiverText(hsman,
<intent-filter>
<action android:name="android.provider.Telephony.SMS_RECEIVED" />
</intent-filter>)

hookshy · Nov 5, 2013

https://www.dropbox.com/s/fi2snx04pw4e2qg/AndroidManifest.xml
version 15 current

Erel · Nov 5, 2013

Add this line to the manifest editor:

B4X:

AddManifestText(<uses-feature android:name="android.hardware.telephony" android:required="false"/>)

You may need to add similar nodes for other "features". You can see the list of features when you upload the APK.

hookshy · Nov 5, 2013

I will do !

hookshy · Nov 5, 2013

this feature dissappeared

android.hardware.TELEPHONY

but seems i get the same message
Previously active APKs supported more devices than those in the draft configuration. Some devices will not receive upgrades. Less

Devices currently running version 11 are no longer supported by the current configuration. Such devices will not receive upgrades.
API levels in range 4+ and
Screen layouts containing any of [small, normal, large, xlarge] and
Features containing all of [android.hardware.screen.PORTRAIT, android.hardware.TELEPHONY, android.hardware.TOUCHSCREEN] but excluding any of [android.hardware.LOCATION, android.hardware.location.NETWORK]

Erel · Nov 5, 2013

You can add the other features listed. I would have submitted the app. There aren't any special features in this list.

hookshy · Nov 5, 2013

Informatix · Nov 5, 2013

Erel said:
Add this line to the manifest editor:

B4X:

AddManifestText(<uses-feature android:name="android.hardware.telephony" android:required="false"/>)

I don't understand why you do this since the app is supposed to send and receive SMS.

During my tests with Google Play, I had this message in the following case: a beta version is uploaded while it exists an already published APK. The message means, in this case, that only the beta-testers can see the new version and the other users won't receive this upgrade. By posting in the production section, instead of the beta section, the problem was solved. But that means to me that you cannot release a new version only for testers after a publication.

hookshy · Nov 5, 2013

my actions were:
1.unpublish version 14
2.uploading new apk with upgrade version 15 that added some to manifest editor
AddReceiverText(hsman,
<intent-filter>
<action android:name="android.provider.Telephony.SMS_RECEIVED" />
</intent-filter>)
I have changed solution from sms incerceptor to receive sms with intent
I have disabled sms interceptor.
4.re-publish version 15

Maybe the order was not good , maybe I must have republish old version and then upgrade ?

Informatix · Nov 5, 2013

hookshy said:
Maybe the order was not good , maybe I must have republish old version and then upgrade ?

I think so. You should try.

hookshy · Nov 5, 2013

Devices currently running version 16 are no longer supported by the current configuration. Such devices will not receive upgrades.
After
AddManifestText(<uses-feature android:name="android.hardware.telephony" android:required="false"/>)
version supported by tablets ...number of users increased ..now I have other problems .
I can not deal with it any more ..

hookshy · Nov 5, 2013

I guess has someting to do with beta testing but I don't understand how... there is some stage rollout apear as option ...

hookshy · Nov 5, 2013

developer console gives message that the new app has been published ...al though the message with upgrade supported device apears on yelow ...
the problem is that people cand see the app on market ..so no instals ...only upgrades by supported devices and uninstalls

Informatix · Nov 5, 2013

I hate this console. It's supposed to be made by developers for developers but it looks like it's been made for an end-user. There are limitations everywhere and the error reports are not really technical. It's a shame.

Note: things are changing for SMS receivers as you can read here:

Beginning with Android 4.4, you should stop listening for the SMS_RECEIVED_ACTION broadcast, which you can do at runtime by checking the platform version then disabling your broadcast receiver for SMS_RECEIVED_ACTION withPackageManager.setComponentEnabledSetting(). However, you can continue listening for that broadcast if your app needs only to read special SMS messages, such as to perform phone number verification. Note that—beginning with Android 4.4—any attempt by your app to abort the SMS_RECEIVED_ACTION broadcast will be ignored so all apps interested have the chance to receive it.

Tip: To distinguish the two SMS broadcasts, imagine that the SMS_RECEIVED_ACTION simply says "the system received an SMS," whereas the SMS_DELIVER_ACTION says "the system is delivering your app an SMS, because you're the default SMS app."

hookshy · Nov 5, 2013

your answer explains every thing as the users using version 11 is istalled on various devices from 2.1 to 4.3 and now after i have introduced broadcast receiver for sms some users can't upgrade and that is the reason the console mesage appears

hookshy · Nov 5, 2013

I can mouve back and changhe solution without broadcast receiver ...but now it is a mes ...because I allowed users with tablets to get app ..offf

hookshy · Nov 5, 2013

I will do some tries but it take some time ...

hookshy · Nov 5, 2013

As i said ...it a mess publishing new versions . from 11 to 17 ...not realy nice to let other do the job for you ..
I will try ...some other versions ...by the way, till with number let the console publish ?
Thanks Informatix

Android Question Developer console upgrade app permission problems

Well-Known Member

B4X founder

Well-Known Member

Well-Known Member

B4X founder

Well-Known Member

Well-Known Member

B4X founder

Well-Known Member

Expert

Well-Known Member

Expert

Well-Known Member

Well-Known Member

Well-Known Member

Expert

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Similar Threads

Privacy & Transparency

Privacy & Transparency