Android Question Request to fix bug in B4A for APK submission to Play Store, targeting SDK 34

[abilio486software]

We are using ‘Receivers’ and when we register them, in a version that points to SDK 34, an error occurs saying that it is not EXPORTED.

If we change the target to Android 33, it works.

But Google won't let you submit APKs if they're not for Android SDK 34.

We urgently need the RegisterReceiver to be able to allow EXPORTED or NOT EXPORTED, so that we can update our app in the Play Store.

Urgent request!

Thanks
Abilio

 

[josejad]

Related

One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts

Hello, I am using the PhoneEvents library in SDK35, but I am facing this error *** Service (starter) Create *** ** Service (starter) Start ** ** Activity (main) Create (first time) ** ** Activity (main) Resume ** Start *** Service (handlerequests) Create *** ** Service (handlerequests) Start **...

www.b4x.com

 

[abilio486software]

Related

One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts

Hello, I am using the PhoneEvents library in SDK35, but I am facing this error *** Service (starter) Create *** ** Service (starter) Start ** ** Activity (main) Create (first time) ** ** Activity (main) Resume ** Start *** Service (handlerequests) Create *** ** Service (handlerequests) Start **...

www.b4x.com

I'd seen that one, but thank you very much.

Broadcast.registerReceiver("......")

It only works if it's targeted to SDK 33
It must be solved because Play Store only accepts APKs targeted for SDK 34.

 

[drgottjr]

something doesn't sound right here. you can set your receivers to be exported or not
in your manifest. when you refer to "registering" your receivers, this sounds like you
are using dynamic receivers, not manifest-declared receivers. is that the case? what
does your manifest look like? if you're using context-declared receivers, you set a flag
to export at time of registration.

 

[abilio486software]

something doesn't sound right here. you can set your receivers to be exported or not
in your manifest. when you refer to "registering" your receivers, this sounds like you
are using dynamic receivers, not manifest-declared receivers. is that the case? what
does your manifest look like? if you're using context-declared receivers, you set a flag
to export at time of registration.

Many thanks for your help.

We are using this code:

'Called when an intent is received.
'Do not assume that anything else, including the starter service, has run before this method.
Private Sub Receiver_Receive (FirstTime As Boolean, StartingIntent As Intent)
    If FirstTime=True Then
       
        Broadcast.Initialize("Taxitronic")
       
        'Service.StopAutomaticForeground 'Call this when the background task completes (if there is one)
        Broadcast.addAction("Taxitronic.LastTripData.Response")
        Broadcast.addAction("Taxitronic.InTripData.Response")
        Broadcast.addAction("Taxitronic.InStopData.Response")
       
        Broadcast.SetPriority(2147483647)
       
        Broadcast.registerReceiver("Taxitronic.LastTripData.Response") 'here you can add the main action (intent)
        Broadcast.registerReceiver("Taxitronic.InTripData.Response") 'here you can add the main action (intent)
        Broadcast.registerReceiver("Taxitronic.InStopData.Response") 'here you can add the main action (intent)
       
    End If
End Sub

And our manifest have:

AddApplicationText(
                   
                    <receiver android:name="taxitronic"
                              android:exported="true" >
                              <intent-filter>
                                     <action android:name="Taxitronic.LastTripData.Response"/>
                                     <action android:name="Taxitronic.InTripData.Response"/>
                                     <action android:name="Taxitronic.InStopData.Response"/>

                              </intent-filter>
                    </receiver>
                )
               
               
AddReceiverText(taxitronic, <intent-filter> <action android:name="Taxitronic.LastTripData.Response" exported="true"/></intent-filter>)
AddReceiverText(taxitronic, <intent-filter> <action android:name="Taxitronic.InTripData.Response"  exported="true"/></intent-filter>)
AddReceiverText(taxitronic, <intent-filter> <action android:name="Taxitronic.InStopData.Response"  exported="true"/></intent-filter>)

With SDK targeted to 33 works perfectly.

If we target to SDK 34, does not work, fires this exeption:

One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts

 

[Erel]

Please upload the AndroidManifest.xml file.

 

[abilio486software]

Please upload the AndroidManifest.xml file.

 

[drgottjr]

i don't know how you managed to do this, but my guess is your so-called ".broadcast" receiver didn't make it to the manifest:

<receiver android:name="taxitronic" android:exported="true">
<intent-filter>
<action android:name="Taxitronic.LastTripData.Response"/>
<action android:name="Taxitronic.InTripData.Response"/>
<action android:name="Taxitronic.InStopData.Response"/>
</intent-filter>
</receiver>
<receiver android:name="broadcast" android:exported="true">
<intent-filter>
<action android:name="Taxitronic.LastTripData.Response"/>
<action android:name="Taxitronic.InTripData.Response"/>
<action android:name="Taxitronic.InStopData.Response"/>
</intent-filter>
</receiver>


<receiver android:name=".taxitronic" android:exported="true">
<intent-filter>
<action android:name="Taxitronic.LastTripData.Response" exported="true"/>
</intent-filter>
<intent-filter>
<action android:name="Taxitronic.InTripData.Response" exported="true"/>
</intent-filter>
<intent-filter>
<action android:name="Taxitronic.InStopData.Response" exported="true"/>
</intent-filter>
</receiver>

that library you're using is very old. it looks like it isn't going to work with sdk34. it's not a b4a bug.
the library's registerReceiver() method does not include the additional parameter for setting the export flag (required for sdk34).
but you should still be able to set the receiver's attribute with the manifest editor with SetReceiverAttribute(myReceiver, "android:exported", true) or false.
more troubling is why the .broadcast receiver doesn't appear in the manifest. i think that's why you see the exception.

by the way, did you actually receive approval from google for your specialuse foreground service? how difficult was that?

 

[drgottjr]

you know, you don't need to register a receiver in code. just declare it in the manifest; it's automatically "registered". you can set your export flag.

 

[Erel]

1. This is not a bug in B4A.
2. You should have posted the full error message.
3. You haven't provided enough information in the first post. Where does "RegisterReceiver" come from?

For further assistance please start a new thread.

 

[abilio486software]

[RESOLVED] SDK 34, Broadcast Receiver, Unable to start.

Hello I will try to be very specific in relation to this issue. I have a service, svc_br_receiver, and in that service I use broadcast receiver lib. The lib has a method called registerReceiver. Under SDK 34 it fails with the following: svc_br_receiver_service_create (java line: 300)...

www.b4x.com

1. This is not a bug in B4A.
2. You should have posted the full error message.
3. You haven't provided enough information in the first post. Where does "RegisterReceiver" come from?

For further assistance please start a new thread.

Erel asked me for the manifest and I sent it, then I get this reply from you...

Unfortunately, Erel's laconic response didn't help at all.

The error wasn't with B4A, it was with the BroadcastReceiver library (I don't know who made it).

BroadcastReceiver can't register, you have to work around it, as Erel pointed out on June 17, 2024:

https://www.b4x.com/android/forum/t...-receiver-unable-to-start.162121/#post-994503

Anyway, it's been resolved but Erel could have helped...

 

[aeric]

The error wasn't with B4A, it was with the BroadcastReceiver library (I don't know who made it).

Always try to use the forum search.
I found the library was created by XverhelstX in 2011.

BroadcastReceiver

Hey, I'm proud to announce another library of mine: BroadcastReceiver. I will try to explain as hard as I can, as I didn't went in to deep in broadcasting and stuff. So, the Android Operating System sends all kind of messages around where the normal users can't see thse. These are called...

www.b4x.com

 

[PJLPJLPJL]

Is this what you need?

[RESOLVED] SDK 34, Broadcast Receiver, Unable to start.

Hello I will try to be very specific in relation to this issue. I have a service, svc_br_receiver, and in that service I use broadcast receiver lib. The lib has a method called registerReceiver. Under SDK 34 it fails with the following: svc_br_receiver_service_create (java line: 300)...

www.b4x.com

 

[abilio486software]

Is this what you need?

[RESOLVED] SDK 34, Broadcast Receiver, Unable to start.

Hello I will try to be very specific in relation to this issue. I have a service, svc_br_receiver, and in that service I use broadcast receiver lib. The lib has a method called registerReceiver. Under SDK 34 it fails with the following: svc_br_receiver_service_create (java line: 300)...

www.b4x.com

Yes, it's already solved with that solution!

Many thanks ?