Frequently Asked Questions
Welcome to the Frequently Asked Questions section of the Group Link One SDK.
This guide brings together clear and objective answers to the main questions that may arise during and after the integration of the SDK into your application.
The guidance covers the native implementations for Android and iOS, as well as every cross-platform integration documented here.
If you do not find your question, please contact our support team.
Compatibility and impact on application size
Which platforms and development frameworks are supported?
Native Android and iOS, as well as the documented cross-platform frameworks: Flutter, Ionic, React Native, Expo, Kotlin Multiplatform and OutSystems. Each framework has its own guide in the SDK documentation.
What are the minimum supported operating system versions?
For native integrations, the minimum versions are Android 6.0 (API level 23) and iOS 15.0.
Cross-platform integrations may require higher minimum versions, imposed by the framework itself and not by the SDK. Always check the guide for the framework you are using before defining the compatibility range of your application.
What is the impact of the SDK on my application size?
Approximate reference values:
| Platform | Approximate size |
|---|---|
| Android | ~ 1.2 MB |
| iOS | The distribution package is ~ 6 MB, as it contains builds for several architectures (iOS, macOS and Simulator); Only the build matching the target device is embedded into the published application, which amounts to ~ 1 MB |
The final impact on the size perceived by the end user is usually smaller, because the app stores optimize the package delivered to each device. These values vary slightly between versions.
Permissions
Which permissions does the SDK require?
The exact list, with the declarations and the runtime requests for each platform, is in required permissions on Android and required permissions on iOS.
I have already added the SDK — why does my application still need to declare the permissions?
The operating system grants permissions to the application, not to the components it embeds. That is why configuring permissions is a mandatory step in every guide.
Why does the Android integration mention a permission for full-screen notifications?
The USE_FULL_SCREEN_INTENT permission is used by our SDK to display the notification in full screen at the moment the device comes into contact with a Bluetooth device, enabling the sensor to start a full-screen intent to process the signal workflow.
Which location dialogs appear on iOS, and when?
Three different dialogs may be presented, and only the first is under your application's control:
- Location permission request — displayed when your application requests it at runtime. It must be requested during onboarding, with a clear explanation of the purpose.
- Background location request — displayed when your application requests it at runtime, after the location permission has been granted, or launched automatically by iOS on its own initiative.
- Notice about background usage — displayed by the operating system (iOS), informing the user how many times the application used the location in the background. It is displayed at the discretion of the operating system (iOS); your application and the SDK do not control when it appears.
Explaining the reason for using the location during onboarding has a direct impact on the number of users who keep the broader authorization, affecting the volume of information collected.
What happens if the user denies one of the permissions?
The SDK adapts to the permissions granted: it keeps operating with lower effectiveness. It does not interrupt your application and does not display error messages.
Does the SDK track my users' location continuously?
No. The location is captured at specific moments, not continuously, and grouped into an H3 cell map, which does not contain the exact position of the devices.
Behaviour in production
Is the behaviour identical on Android and iOS?
The SDK offers the same capabilities on both platforms; however, the two operating systems manage Bluetooth and location in different ways.
Battery and data usage
How much battery does the SDK consume?
The SDK is designed for low impact: it uses the low-energy Bluetooth radio (BLE), requests the location only at specific moments instead of keeping it continuously active, and remains idle when there are no relevant signals nearby.
The measured impact depends on the device model, the operating system version and mainly on how much time it spends near Group Link devices.
How much mobile data does the SDK use?
Very little. Each transmission carries a few kilobytes and periods with no relevant device nearby generate practically no traffic.
SDK Updates
How are new SDK versions released?
New SDK versions are published through the standard package managers of each platform:
| Platform | Package manager |
|---|---|
| iOS | CocoaPods and SPM |
| Android | JitPack |
| Flutter | pub.dev |
| Ionic, React Native and Expo | npm |
| OutSystems | Forge |
It is extremely important to always keep the SDK up to date, as new versions bring improvements, bug fixes and new features.
Did not find your question?
Consult the SDK documentation, which covers installation, permissions and initialization step by step.
If the question remains, contact our support team.
Last updated: September 16, 2026