Android Question [solved] Targeting SDK 34 (emergency)

[udg]

Hi all,
for several reasons it's a while since I last could spend time programming.
Now, a customer of mine forwarded a mail where Google announces they will shut down his accont if there's no upgrade of their only app (made by me).
The emergency in the title depends on the fact I'm not able at this time to upgrade my B4X tools.

So, can I use my current 12.50 installation simply targeting sdk 34 in Manifest to publish a fake upgrade of the app?
Will it suffice to write in manifest:
<uses-sdk android:minSdkVersion="24" android:targetSdkVersion="34"/>
to have Google accept it (along with an higher VersionCode) as an upgrade in order to postpone the deadline to a later time when I'll be able to upgrade my B4X tools?

I seem to recall it was possible if not services where involved (but the empy Starter service). Am I right?

Besides increasing the "targetSdkVersion" value, any other hint to make it acceptable?

TIA
udg

 

[JohnC]

Posting the exact text of the email could offer us some more clues. But, yes - you might be able to simply update the target sdk and resubmit.

However, when you do this, it may break things in your app because the higher target level might now restrict certain activities of your app that you will need to address/fix.

 

[Chris2]

You or your customer may be able to extend the deadline to take the pressure off....

[INFO] Moving to SDK 34 on the Playstore

Hello All Anyone who is feeling under pressure to upgrade to 34 as per Google Playstore requirments, you can get an extention (instant) to November 1st 2024. I have done this already, I suggest you all do the same. It is done through the play console. Regards John.

www.b4x.com

 

[drgottjr]

basically echoing what these guys said above:

someone posted here that you can request an extension until november...

if more than simply targeting 34 is required, then your update will be rejected
and customer's account closed. if you do nothing, the account will be closed.

target 34 and see what happens. i targeted a couple apps to 34 last month (before we
had b4a 13) and updated. no problem. of course, i have no idea what your app does.
most of the changes are going to involve permissions. the longer you wait to find out,
the harder it will be to make changes by aug 31. i'm guessing google simply tries to
run your app under 34 ... you might even find out within 24 hours.

and see what the story is regarding extension. the forum member said it was automatically
granted.

 

[Shelby]

Yes, as Chris said, you can ask for more time. I was just there and there is a button asking for that time extension. In addition I think Dr. Gott is also correct; so either way will give you a temporary fix at least.

 

[udg]

Thank you @JohnC
The mail forwarded to me reads:
Your developer account is not in use. Play Console developer accounts are intended for developers who actively publish and maintain apps. To protect the safety of app users, developer accounts that aren't used are closed. Learn more
How to fix this
If you plan to publish or maintain apps in the future, prevent your account from being closed by completing the following tasks:

• If you haven't done so yet, verify your email address and phone number on the Account details page
• Create and publish an app, or publish an update to an existing app on Google Play. Learn more

Fix this before September 9, 2024 to prevent your account from being closed.

This is really a wise note:
However, when you do this, it may break things in your app because the higher target level might now restrict certain activities of your app that you will need to address/fix.
I've to check, but I can't recall about special Permissions or anything "unusual". Anyway I'll look in the code to be sure.

@Chris2 , @drgottjr, @Shelby : thank you all. I'll check for the deadline extension first.

 

[RichardN]

I checked through my 6 or so paid apps for the issues (mostly services) that have been discussed in the forum. I was a little worried about the result, but having satisfied myself that none of the SDK34 issues affected me I installed 34 and went about testing them all with TargetSDKversion=34. When I was satisfied that all was well I took a leap of faith and published. No problems since.

But @udg I am slightly puzzled..... If your customer is the only user of this app, why are you bothering with the Play store? Surely you can get around all the Google BS by installing manually. That way the customer does not have any need to deal with Google or their ever changing requirements, although you will have to watch out for functions that might become broken with later Android versions and handset upgrades.

 

[JohnC]

Thanks for posting the email....so now it's clear that google is not requiring you to specifically update the app to SDK 34, it is simply saying it needs to see some activity on the account, and simply updating the targetSDK to 34 should address their concern (as long as the app works at that level).

 

[Shelby]

If you will or have already updated your personal information on Google Play console, I think they will be satisfied about your action to satisfy their email warning you have mentioned. I too was asked to verify my info.

 

[RichardN]

It also raises the question: Having written an app for a customer, for a particular handset, is the programmer forever responsible to the customer when he upgrades the handset and discovers that the app is now broken due to an Android version change?

I had a well-selling app that I withdrew from sale in 2016 for a major re-write. The new app was published and sells even better. Unfortunately the original app went on to around 2022 before a lack of my upgrades and new Android versions in new handsets would no longer run. It all depends on the likely revenue for your work to bring the app up to date. You cannot be responsible for Google's upgrades forever.

 

[Shelby]

Now I have to admit I have the same old damn problem of the target version not accepted on my newest app. Crap! I've tried three times to upload a bundle where my target is:

AddManifestText(
<uses-sdk android:minSdkVersion="5" android:targetSdkVersion="34"/>
<supports-screens android:largeScreens="true"
    android:normalScreens="true"
    android:smallScreens="true"
    android:anyDensity="true"/>    )
SetApplicationAttribute(android:icon, "@drawable/icon")
SetApplicationAttribute(android:label, "$LABEL$")
CreateResourceFromFile(Macro, Themes.LightTheme)
'End of default text.


'following new 8/12/24 from Erel "Google Play Billing - In App Purchases
CreateResourceFromFile(Macro, GooglePlayBilling.GooglePlayBilling)

Still Google Play screws me. My bundle is bad. I thought I took care of that target sdk 34 a few weeks ago. Maybe I shouldn't have put in that last line about the GooglePlayBilling; I just thought I'd get ahead of the game and start the transition to billing by adding it early.

Consequently I just edited out that line. Uploading bundle again.

 

[udg]

@RichardN : it's not a single user but one customer (a company) who decided to enroll as a developer.
So I created an email for them, then the dev account. I developed the app and published it (on Android and iOS stores). After that, based on the initial agreement, I gave them the source and any useful account data. This is why they forwarded that email to me: I no longer have access to that email account or to the dev account.

Now, letting them to accomplish administrative chores (like the email verification suggested by Google), I will firstly try the "tricks" to move the deadline ahead or, failing, to modify just the Manifest.
If nothing works, I will need to take with me my notebook and find a place where Internet is strong enough to download and install anything needed for B4A 13. I know it sounds easy, but I'm leaving for a short vacation to a place where even phones work at random (yes, a real paradise, in this respect )

When done, I'll post here to close the thread. Thank you all.

Edit: trick#1 (deadline to Novembre 1) accepted but I fear it only covers the time available to update the app; so I will also try trick#2 (Manifest change) hoping it will suffice to clear the risk of account deletion.

Edit#2: app published soon after trick#2 (Manifest change) was applied. The day after, any warnings about dev account suppression or policy violations were removed.