I have an app that has been working fine for years, until I upgraded it to SDK 33. The upgraded version works fine on my Android S10 with Android version 12. There are users with Android version 14 who are complaining that when launching the app they get a blank screen and then message "isn't responding - Close app/wait" appears. I thought at first it was me using Scheduling Alarm Exact so I added this as recommeded by Erel: -
This is my manifest, could something perhaps be wrong with it?
Scheduling Alarm Exact:
Wait For (GetScheduleExactAlarmPermission) Complete (HasPermission As Boolean)
'StartServiceAtExact(ServiceName, NextTimeInstance(DateTime.GetHour(t), DateTime.GetMinute(t)), True)
If HasPermission Then
StartServiceAtExact(ServiceName, NextTimeInstance(DateTime.GetHour(t), DateTime.GetMinute(t)), True) 'yes it is StartServiceAtExact and we pass a receiver
This is my manifest, could something perhaps be wrong with it?
Manifest:
AddManifestText(
<uses-sdk android:minSdkVersion="9" android:targetSdkVersion="33"/>
<supports-screens android:largeScreens="true"
android:normalScreens="true"
android:smallScreens="true"
android:anyDensity="true"/>)
SetApplicationAttribute(android:icon, "@drawable/icon")
SetApplicationAttribute(android:label, "$LABEL$")
AddApplicationText(
<uses-library
android:name="org.apache.http.legacy"
android:required="false" />
)
CreateResourceFromFile(Macro, Core.NetworkClearText)
AddPermission(android.permission.ACCESS_FINE_LOCATION)
AddApplicationText(<meta-data
android:name="com.google.android.gms.version"
android:value="@integer/google_play_services_version" />)
AddPermission(com.android.alarm.permission.SET_ALARM )
AddPermission(android.permission.SCHEDULE_EXACT_ALARM)