@lopespetro this requires Location permission to fetch the GPS coordinates. Can you double check that Location permission is enabled on MWO?

Best regards,

Rukmal

Hi @Rukmal Fernando , yes. the permission is enabled.

In UPD17 it works fine.

@lopespetro by “Location permission” I meant this. How does it compare with yours?

Cheers,

Rukmal

Yes @Rukmal Fernando . This permission is on.

@lopespetro is it the same behaviour on Android and Windows?

and you mentioned that it works on Upd17. Does it mean that the same app works differently against your UPD17 instance and your UPD24 instance? if so, can you the following result for both your environments please? (filtered by App Name: MaintEngApp, App Version: <latest in your env>, Category: %Location%).

Best regards,

Rukmal

Hi @Rukmal Fernando , UPD17 is in PRD envir, and UPD24 is in TST envir.

The TAS also is in differnte server:.

UPD24

IFS Touch Apps Server 10.24.536.1 for Apps10

 UPD17

IFS Touch Apps Server 10.17.442.0 for Apps10

UPD24:

UPD17:

@lopespetro is 1.11 the highest version of MaintEngApp on your UPD17 environment? I was expecting to see 1.17 there.

Yes @Rukmal Fernando , See bellow:

Hi All, I have done more tests and noticed that the problem is just with android. Windows and IOS apps are working as expected.

I’ve tested with android 12 and 14 with owner user, english and portuguese brazil with different devices (motorola and samsung).

Already raised a case CS0301802.

@Bandula @James Ashmore @Rukmal Fernando any ideias?

@lopespetro thanks for raising the Support Ticket, we can then plan it into work streams and do a deeper investigation.

Best regards,

Rukmal

Hi @Rukmal Fernando , any news?

@lopespetro this seems to be under investigation by our Support team and I’m trying to check on the status. We’ll share an update via the ticket once it does reach us.

Best regards,

Rukmal

@lopespetro Have you tested APPS 10 Update 17 and Update 24 with same Android devices and at the same location? Just to confirm if you have the same testing conditions. 

Additionally, the issue may be related to a location pulling delay (a prolonged time to retrieve location data from GPS) on certain Android devices. The Cloud Android App has introduced improvements to address this by implementing location polling with additional providers (such as Cellular Network, WiFi, etc.) and using the last known location, which may help reduce the lag.

Best Regards,

Edward

Hi @elin , yes. same for both UPDs.Tks for the info. I hope the support can come with a solution for APPS10.

Hi ​@Rukmal Fernando, ​@James Ashmore ​@Bandula 

Our local support team has updated our test environment to APPS10 UPD26. I tested it, but the issue persists exactly as before—only on Android.

Even when using the owner user, the problem remains.

Please see the screenshots below. The message disappears without any action, and I need to close and reopen the app for it to work again. Additionally, the location icon appears at the top but disappears after three seconds.

Strangely, this issue does not occur with the IFS Cloud app.

Another thing I’ve noticed: If I disable the "Use precise location" option and try again, the app prompts me for location permission, asking whether I want to switch to precise location or keep the approximate location.

If I choose to keep the approximate location and then try to add media from the camera, the app throws an error (screenshot below). However, after closing the error message, the media uploads successfully, and the sync works correctly.

Do you have any idea what might be causing this?

Thanks!

​@lopespetro sorry, I can’t think of anything that can cause this behaviour. I’ve not seen the Support Case you created, CS0301802. Can you update that and followup via it too please?

Thanks,

Rukmal

hi ​@Rukmal Fernando , please take a look in this case: CS0316415

The local support has created this parent case.

Tks

​@lopespetro CS0316415 is closed on our end due to not being reproducible and no feedback. Since you seem to have a new scenario, I suggest that you liaise with our Support Team to raise a new Support Case with this new information.

Please note that it’s essential for us to find a reproducible test case for any concrete action from the product team.

Best regards,

Rukmal

Hi ​@Rukmal Fernando , I don’t know why the local support closed the case if it’s not resolved yet. But anyway, I opened another one and updated with fresh tests with UPD26.

Case: CS0389453

Today I ran several tests using the following devices, all of them restored to factory settings:

• Samsung Galaxy Tab S6 (SM-P619) – Android 14

• Samsung Galaxy Tab S8 (SM-X706B) – Android 14

• Samsung Galaxy S24 Ultra (SM-S928B) – Android 14

• Motorola Moto G30 – Android 12

Initially, everything worked correctly on all devices. However, after a few minutes of use, the issue started happening again.

After some research, I found that a possible root cause may be related to the combination of the Location API and the Camera API, especially on devices from manufacturers like Motorola and Samsung. These vendors often implement customizations on Android that can interfere with standard Google API behavior — particularly the Google Location API fallback.

It’s worth mentioning that I didn’t face any issues while testing with Xiaomi devices such as:

• Xiaomi 2201117PI

• Xiaomi POCO X2

• Xiaomi Redmi Note 8 Pro

In all of these cases, the process worked flawlessly.

Additionally, I noticed that when I disable the location permission on Android, the media upload (photo) happens immediately, without any freezing or delays.

Given these findings, I’d like to suggest running some tests in the production environment using these devices I have available, so we can further validate this behavior and collect more evidence.

Let me know what you think.