You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.
Hi, I just received the starter kit and stetted up a play ground in react-native 0.61.5.
How exactly does the background mode works? I enabled the backround bluetooth in xCode and my I initialize the proximityObserver with this config:
const config = {
notification: {
title: 'Exploration mode is on',
text: 'We\'ll notify you when you\'re next to something interesting.',
channel: {
id: 'exploration-mode',
name: 'Exploration Mode',
},
},
};
I stetted up remote notification (which I know works) but when the phone is locked I do not receive these notifications. this is my proximityObserver startObserving method:
Okay so I figured I did not have the "always" on the location permissions on.
So I got it to work on Background mode but it does not work when app is closed.
is there any more configuration I need to do in order to make this work?
I'm also trying to detect beacons when the phone screen is off or when the app is minimized, but I can't see how can I ask for "always" location permission in iOS with this package.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, I just received the starter kit and stetted up a play ground in react-native 0.61.5.
How exactly does the background mode works? I enabled the backround bluetooth in xCode and my I initialize the proximityObserver with this config:
I stetted up remote notification (which I know works) but when the phone is locked I do not receive these notifications. this is my proximityObserver startObserving method:
this is not called when the phone is locked.
should I do anything else? am I missing something? I haven't notice any other configuration in the docs.
Thanks
The text was updated successfully, but these errors were encountered: