-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cordova-plugin-ibeacon not working starting android 11 #479
Comments
Happy to help! I was going to ask if you already had it working in a
earlier version of android?
Did you add the necessary permissions for the latest android version?
Also, are you able to see any errors in the console?
…On Thu, Apr 20, 2023 at 2:33 AM RN-programmer ***@***.***> wrote:
We are using cordova-plugin-ibeacon to detect beacons in our android
mobile app.
As per google play store policy, we updated our app compile sdk to 31.
After that, ibeacon not detecting any beacons.
We tried all the changes mentioned in this link :
#474 <#474>
I really appreciate if someone is having a solution for this issue.
—
Reply to this email directly, view it on GitHub
<#479>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQ3FBPSVUIOXEYZRYZZ2CTXCD7E5ANCNFSM6AAAAAAXFHJWEM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hi @noahbaron , Yes I have added all necessary permissions.. Beacons list is coming as empty. |
One permission that changed is Bluetooth permission. There is now a
BLUETOOTH_SCAN permission that is required.
Also, what version of android did you have it working on previously? Did
you have it working with all the necessary android:exported =“false” tags
to AndroidManifest.xml?
…On Thu, Apr 20, 2023 at 11:58 PM RN-programmer ***@***.***> wrote:
Hi @noahbaron <https://github.com/noahbaron> ,
Yes it was working in the earlier versions of android.
Yes I have added all necessary permissions..
App is building and running. But beacons list is coming as empty.
—
Reply to this email directly, view it on GitHub
<#479 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQ3FBMD7NK4FPXDY2QJUD3XCIVXTANCNFSM6AAAAAAXFHJWEM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi @noahbaron , All necessary permissions has been added including BLUETOOTH_SCAN and android:exported="false" for intent filters . But no luck with respect to beacon list. still it's empty. |
@RN-programmer
Here’s a link to my AndroidManifest.xml for reference. I had to add
additional entries based on what I was seeing in the merged manifest and
include the android:exported=“false” tag.
https://github.com/baronbrew/Tilt-Hydrometer-Framework7/blob/master/platforms/android/app/src/main/AndroidManifest.xml
Also, can you confirm that you’re getting permissions for fine location?
You can see this in the manifest as well (see below). In my app I am using
the Cordova permissions plug-in. Have you confirmed you have the fine
location permissions needed as shown when you check the app settings?
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
…On Mon, Apr 24, 2023 at 2:18 AM RN-programmer ***@***.***> wrote:
Hi @noahbaron <https://github.com/noahbaron> ,
All necessary permissions has been added including BLUETOOTH_SCAN and
android:exported="false" for intent filters .
But no luck with respect to beacon list. still it's empty.
—
Reply to this email directly, view it on GitHub
<#479 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQ3FBJDXRA5GTSTVSPJ2MTXCZAMPANCNFSM6AAAAAAXFHJWEM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@noahbaron : Yes I'm having "android.permission.ACCESS_FINE_LOCATION" PERMISSION too.. But not getting the beacons |
Can you copy/paste your log output from Android Studio? Are you seeing any
errors or warnings about permissions or Bluetooth? Also, have you confirmed
your beacon was working with your previous version of your app?
…On Mon, May 1, 2023 at 10:53 PM RN-programmer ***@***.***> wrote:
@noahbaron <https://github.com/noahbaron> : Yes I'm having
"android.permission.ACCESS_FINE_LOCATION" PERMISSION too..
But not getting the beacons
—
Reply to this email directly, view it on GitHub
<#479 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQ3FBNGN6O556ITEQ3D6IDXECONZANCNFSM6AAAAAAXFHJWEM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
We are using cordova-plugin-ibeacon to detect beacons in our android mobile app. It was working till android sdk 29.
As per google play store policy, we updated our android app compile sdk to 31. After that, ibeacon not detecting any beacons.
We tried all the changes mentioned in this link :
#474
I really appreciate if someone is having a solution for this issue.
The text was updated successfully, but these errors were encountered: