[Help Wanted]:

[mahendra-systango]

Required Reading

• Confirmed

Plugin Version

@transistorsoft/capacitor-background-fetch -> ^7.0.1, @transistorsoft/capacitor-background-geolocation -> ^7.0.3

Mobile operating-system(s)

• iOS
• Android

Device Manufacturer(s) and Model(s)

Both Android and iOS

Device operating-systems(s)

iOS > 15 and Android > 10

What do you require assistance about?

We are currently testing the background fetch functionality on multiple devices, including both iOS and Android platforms. During our testing, we have observed that a significant number of records display the Travel Mode as "Unknown." We are unable to determine why "Unknown" is appearing instead of expected values such as "Still" or other relevant statuses.

We have purchased and integrated the plugin, but this issue persists. We kindly request your assistance in investigating and resolving this matter at your earliest convenience.

Our investor had 10,000 data points and, 9000 were unknown, too many unknowns with the application.

Thank you for your support.

[Optional] Plugin Code and/or Config

BackgroundGeolocation.ready({
        // Geolocation Config
        desiredAccuracy: BackgroundGeolocation.DESIRED_ACCURACY_HIGH,
        distanceFilter: this.gfSetByUser,
        url:`${webAdmin.apiAdminUrl}firebase-location/`,
        extras:{email: userId, uid:uid, autorization: token},
        debug: false, // <-- enable this hear sounds for background-geolocation life-cycle.
        logLevel: BackgroundGeolocation.LOG_LEVEL_VERBOSE,
        stopOnTerminate: false,   // <-- Allow the background-service to continue tracking when user closes the app.
        startOnBoot: true,        // <-- Auto start tracking when device is powered-up.
        backgroundPermissionRationale:{
          // title: "Location Permission",
          message: "This app collect location data for track travel emissions",
        }
      }).then((state) => {
        // BackgroundGeolocation is now ready to use.
        this.isInitializing = false;
        this.ready = true;
        this.enabled = state.enabled;
        this.isEnabled$.next(this.enabled);
        this.addEvent('State', state);
      }).catch(err=>{
        this.isInitializing = false;
        console.error("ready state added error");
        console.error(err);
        // this.logFirebaseEvent('ready:error', { error: err }).catch(()=>{});
      });

[Optional] Relevant log output

https://ibb.co/MxfYh1wL

[christocracy]

The motion API for both iOS and Android is a "black box" with nothing more than an ON/OFF switch. The plugin has no control over the results of these APIs.

Note: the motion doesn't work in simulators, only real devices. You user must grant the runtime permission for motion / health.

[mahendra-systango]

Hi, Thanks for your Reply. We have checked and found that. We are getting this error on the iOS only and we have checked with iOS version 26.1.

As we have mentioned we are using the plugin version

@transistorsoft/capacitor-background-fetch -> ^7.0.1, @transistorsoft/capacitor-background-geolocation -> ^7.0.3

Also, we are using angular 18, Can you please suggest if we need to upgrade the plugin? or any other suggession.

[christocracy]

Your problem has nothing to do with Angular or plug-in version.

You simply need to apply the "Motion Usage Description" in your Info.plist, as directed in the Setup Instructions.

After that, it's up to the user to grant the "Motion" runtime permission when prompted by the OS. If the user does not grant that permission, then your app is not allowed to have Motion information, thus "unknown".

[mahendra-systango]

Plugin Updates

We have updated the plugin with the latest one.

Checked configuration

We have checked the configuration for the background fetch, and found all are correct we have followed

https://github.com/transistorsoft/capacitor-background-geolocation/blob/a4b38d612337ecaa197381749b3155c64b406820/help/INSTALL-IOS.md

https://github.com/transistorsoft/capacitor-background-fetch/blob/master/help/INSTALL-IOS.md#configure-background-capabilities

Confiuguation

We have found all the configuration are correct as mentioned in the above given documents.

We have received the the activity for around 24 hours but after 24 hours it again started giving Unknown

Checked the Permission

We have also allowed the motion and location permission I have attached the video for the same permission.

https://drive.google.com/file/d/1de7Ed4f6S_sMlo7JA1ClsS9_8GwFR8YD/view?usp=sharing

Still we are getting the Unknown activity type.

[christocracy]

The motion api information is provided by the OS. This api exposes nothing more than an ON/OFF switch. The plug-in has nothing to do with quality of the data. It's merely the mailman.

Try rebooting your device.

[mahendra-systango]

It is not related to speicific devices we have around 32 to 35 members who are running the application we are getting Unknown activity type for all.

[mahendra-systango]

Hello,

In the android we are getting still always. Earlier, we were getting the different modes like walking, in_vehicle, on_bicycle, etc. But now we are getting still only. Can you suggest what we need to do to fix this.

[christocracy]

Try rebooting your device.