Mobile Developer Answers & Best Practices - Recent Threads

RE: Getting too many API calls when APP is idle

Eugene Bychkov — Mon, 09 Mar 2026 16:08:17 GMT

Make sure to double check

This is exactly what you get when offline mode is enabled

Dialog 'Do you want to download your records' is only shown when offline mode IS ENABLED

Getting too many API calls when APP is idle

Raghavendra Karunakar — Fri, 27 Feb 2026 06:17:30 GMT

Hi Team,

I have created a sample App using Mobile-sdk version 87.0.850-1.4.2-2

I've noticed excessive background API calls, even when the application is idle.

As we are dealing with high volumes of production data, this can cause performance issue.

I need to identify and disable these unnecessary requests.

Requesting anyone to help on this.

I have attached screenshot for reference.

Thanks in Advance.

RE: Getting too many API calls when APP is idle

Raghavendra Karunakar — Mon, 09 Mar 2026 11:43:17 GMT

Hi Eugene Bychkov

Thanks for the reply!!

The offline Mode is already disabled in the App, even after login a page is shown to download offline records that also I have selected "Not right now".

Still the API gets triggered while using the app or when App is idle.

I don't think this is related to Offline Mode.

RE: Getting too many API calls when APP is idle

Eugene Bychkov — Fri, 06 Mar 2026 08:12:48 GMT

Raghavendra Karunakar this is expected functionality
when offline mode is turned ON on the device, Sugar Mobile periodically performs requests to server to fetch and synchronize new records from server to device database

see this doc support.sugarcrm.com/.../

you can disable this by:

1. turning OFF offline mode either in admin->mobile or on device

2. modifying config file in your app. see this property: jsConfig.offline.syncManager.executors.wins.enabled and set it to false

Best regards, Eugene

RE: Getting too many API calls when APP is idle

Raghavendra Karunakar — Fri, 06 Mar 2026 06:53:00 GMT

Eugene Bychkov Development Team
Request you to please provide some solution.

RE: Guidance on Mobile App Upgrade (v45 → v87) and Long-Term Support Strategy

Eugene Bychkov — Mon, 22 Dec 2025 05:06:03 GMT

Whether upgrading from v45 to v87 would require a complete or partial rewrite of our existing mobile custom code due to the transition to React. - most likely not much of your custom code will have to be rewritten. React was introduced mostly in new components/functionality, so your existing customizations are most likely not affected
Which legacy mobile customization frameworks or APIs are deprecated or no longer supported in the latest versions - it's hard to tell from top of my memory, most likely nothing major was deprecated
Recommended migration strategy or best practices for converting existing Cordova/Backbone-based customizations to the React-based mobile framework - see point number one. Each component will need to be managed by hand depending on kind of customization, there is no 'official' way unfortunately
Availability of any official documentation, migration guides, or tools to support this conversion - no special tools are available here
Which SugarCRM Mobile versions or upgrade paths are best suited for long-term stability and support - From my perspective, the best way for long-term stability would be to migrate codebase in a small steps with each new mobile SDK release to avoid big jumps (like in this case) that could introduce significant hurdles
See point 5
No official guidelines are available, so please stick to general engineering best-practices

Long-term roadmap for Sugar Mobile is not clear at this point. For now, no breaking changes are planned

Best regards, Eugene

Guidance on Mobile App Upgrade (v45 → v87) and Long-Term Support Strategy

Chetan Ghaydar — Fri, 19 Dec 2025 07:15:09 GMT

Dear SugarCRM Support Team,

We are planning to upgrade our custom SugarCRM Mobile application from version 45.0.657-1.4.2-2 to 87.0.850-1.4.2-2 and would like to seek your guidance before initiating this activity.

Our existing mobile application includes extensive customizations developed using Cordova and Backbone-based components, as supported in version 45. In the newer SugarCRM Mobile versions, we understand that there has been a significant architectural shift, with React-based technology introduced and much of the functionality migrated away from Cordova and Backbone.

In this context, we would appreciate your advice on the following:

Whether upgrading from v45 to v87 would require a complete or partial rewrite of our existing mobile custom code due to the transition to React.

Which legacy mobile customization frameworks or APIs are deprecated or no longer supported in the latest versions.

Recommended migration strategy or best practices for converting existing Cordova/Backbone-based customizations to the React-based mobile framework.

Availability of any official documentation, migration guides, or tools to support this conversion.

Additionally, from a long-term support perspective, we would like your guidance on:

Which SugarCRM Mobile versions or upgrade paths are best suited for long-term stability and support.

Recommendations on how to design or refactor mobile customizations to minimize rework in future upgrades.

Any SugarCRM-supported standards or architectural guidelines we should follow to ensure our mobile application remains compatible with future releases.

Given the scale of these changes, we want to ensure our upgrade and redevelopment approach aligns with SugarCRM’s supported technologies and long-term roadmap, while avoiding unsupported customization patterns.

We appreciate your guidance and look forward to your recommendations on how best to proceed.

Thanks & Regards,

Chetan Ghaydar

RE: Guidance on Mobile App Upgrade (v45 → v87) and Long-Term Support Strategy

Chetan Ghaydar — Mon, 22 Dec 2025 04:13:08 GMT

Eugene Bychkov Please help here!!

RE: The client’s application remains stuck in offline mode, and even after switching to online mode, it continues to operate offline despite active network availability. This issue is directly impacting the client's production operations.

Chetan Ghaydar — Wed, 10 Dec 2025 10:35:35 GMT

Eugene Bychkov Will check this!! and Update,

Please go through the image below I forgot to upload in last msg. The device is online for other applications still it is show offline in Sugar & internet is on

The client’s application remains stuck in offline mode, and even after switching to online mode, it continues to operate offline despite active network availability. This issue is directly impacting the client's production operations.

Chetan Ghaydar — Tue, 25 Nov 2025 07:50:28 GMT

Problem Statement:
The client’s application remains stuck in offline mode, and even after switching to online mode, it continues to operate offline despite active network availability. This issue is directly impacting the client's production operations.

Detailed Description:
The client is experiencing a persistent issue where the application does not transition to online mode once it has gone offline, even when a stable network connection is present. They are currently using an older SDK version (83.0.831-1.4.2-2). While we understand that the SDK is outdated, we would like to understand what specific conditions or system behaviours could cause such an issue.

This is a custom application; however, we have not altered any core functionalities. All development has been done strictly through extensions, and there are no custom features that could interfere with this part of the core offline/online logic.

We have tested the scenario across multiple environments and network conditions, but we have been unable to replicate the issue on our end, including:

Device Simulator
2G Network
Wi-Fi
Regular broadband/mobile data
Client’s 5G network environment

Despite these repeated tests across different conditions, we have been unable to identify the root cause or find a workable resolution.

The client reports that on the vanilla app downloaded from the Play Store, the issue does not occur — it successfully switches to online mode. This further increases their concern, and they are becoming increasingly impatient as this affects day-to-day operations.

We are ready to share the relevant code snippets for your review, should you require them.

We kindly request your assistance in helping us identify the possible root causes of this behaviour and guide us on the next steps toward resolution. Understanding what in the SDK, configuration, or environment could cause the offline mode to remain stuck would be highly valuable for troubleshooting. If required, we are will open a Sugar Development Support ticket for the same.

RE: The client’s application remains stuck in offline mode, and even after switching to online mode, it continues to operate offline despite active network availability. This issue is directly impacting the client's production operations.

Eugene Bychkov — Wed, 10 Dec 2025 10:28:44 GMT

Hi Chetan
I am glad to hear that you are making progress
However as this issue is so tightly related to a specific device I don't think there is any help that we can provide from our side

I suggest you to do the following:

1. build your app in debug mode

2. after that you will be able to connect to WebView using standard Android/iOS methods
https://developer.chrome.com/docs/devtools/remote-debugging/webviews

https://medium.com/@atifqamar29/debugging-ios-webviews-on-safari-browser-822def097497

3. or debug in your desktop chrome

4. click through the app, use steps that are known to cause issues, and inspect console for errors and network tab for AJAX errors

maybe this will help you to get on the right track

RE: The client’s application remains stuck in offline mode, and even after switching to online mode, it continues to operate offline despite active network availability. This issue is directly impacting the client's production operations.

Chetan Ghaydar — Wed, 10 Dec 2025 10:10:29 GMT

Thanks Eugene Bychkov !!

During a troubleshooting session with the client, we tested three different APK versions:

Old SDK with customisations (83.0.831-1.4.2-2)
Old SDK without customisations (83.0.831-1.4.2-2)
Latest SDK without customisations (87.0.850-1.4.2-2)

Observations:

On Device A, all three APKs worked without any issue.
On Device B, all three APKs displayed the offline mode message.

This indicates that the issue is not related to the customisations or the usage of an older SDK version.

Additional findings:

Both devices were on the same network, and on the device where the issue occurred, other apps and internet connectivity were functioning normally.
When we logged in using the affected user credentials on Device A (where apps were functioning), the login worked without any issue.
However, logging in with the same user credentials on Device B reproduced the offline mode issue.
The client also confirmed that the issue occurs randomly for different users, suggesting it may be related to specific user accounts rather than the device or app build.
We checked pending transactions at the time of issue reproduction, and there were none.
We have attached the relevant screenshot showing the offline message for clarity.

We would like to schedule a call with your team to discuss potential root causes and next steps for identifying and resolving this behaviour.

If helpful, we can also share a video recording of the troubleshooting session (cropped to the relevant portion). Please confirm if you would like us to provide it.

Looking forward to your guidance.

RE: The client’s application remains stuck in offline mode, and even after switching to online mode, it continues to operate offline despite active network availability. This issue is directly impacting the client's production operations.

Eugene Bychkov — Fri, 28 Nov 2025 08:45:03 GMT

Hi Chetan,
Please take you time to study these docs: https://support.sugarcrm.com/documentation/mobile_solutions/sugarcrm_mobile/sugarcrm_mobile_app_user_guide/#Transaction_Log

In your case application can be 'stuck' in offline mode if some transaction (create, update, detele, etc operation) can not be synced with server for some reason (e.g. server error, no access, or smth)

Something like this could have happened:

- User goes offline

- User does some modification to a record

- User goes back online

- Sugar Mobile tries to sync changes made while offline with server but fails

- In this case Sugar Mobile will stay in offline mode and queue all further operations after initial operation

- but no operations will go to server until initial transaction is resolved (this is done to preserve data consistency)

So in your case you should debug this scenario to see if this is what really happens.

Potentially, do this with customer's instance clone to observe custom instance peculiarities

Then investigate why some transactions (error codes, see server logs, etc) are not accepted by the server

Hope this helps, Eugene

RE: The client’s application remains stuck in offline mode, and even after switching to online mode, it continues to operate offline despite active network availability. This issue is directly impacting the client's production operations.

Chetan Ghaydar — Fri, 28 Nov 2025 08:09:13 GMT

Club Concierge Brie Rowe Alex Nassi Eugene Bychkov Could you please help here!!

RE: Clarification on Gzip Support in SugarCRM Mobile SDK

Eugene Bychkov — Mon, 22 Sep 2025 09:34:38 GMT

Chetan, with SDK you get FULL access to Sugar Mobile source code
If it is technically possible, then it can be integrated into SDK

Best regards, Eugene

Clarification on Gzip Support in SugarCRM Mobile SDK

Chetan Ghaydar — Tue, 16 Sep 2025 07:29:18 GMT

I would like to confirm whether the SugarCRM Mobile SDK supports Gzip compression for API requests and responses.

Does the Mobile SDK automatically handle Gzip-compressed responses from the SugarCRM server, or do we need to implement any additional configuration/code to enable this?

If supported, is there any official documentation available for reference?

We are evaluating the SDK for a mobile customization project and want to ensure Gzip is supported out-of-the-box to optimize performance.

Thank you for your assistance.

RE: Clarification on Gzip Support in SugarCRM Mobile SDK

Chetan Ghaydar — Mon, 22 Sep 2025 07:48:45 GMT

Is it possible to integrate Gzip with mobile SDK?

RE: Clarification on Gzip Support in SugarCRM Mobile SDK

Eugene Bychkov — Mon, 22 Sep 2025 07:27:46 GMT

Hi Chetan!
We have no explicit logic regarding Gzip compression, so we don't explicitly do gzipping or forbid it either

All AJAX requests handled by underlying WebView component powering Sugar Mobile. It seems that you need to do some investigation regarding that to confirm your requirement or idea.

Best regards! Eugene

RE: Clarification on Gzip Support in SugarCRM Mobile SDK

Chetan Ghaydar — Mon, 22 Sep 2025 06:01:18 GMT

Eugene Bychkov Can you please help me here?

RE: Mobile App Heap Size Issue – Investigation & Support Request

Eugene Bychkov — Tue, 02 Sep 2025 10:29:22 GMT

1. there are no explicit limitations in Sugar Mobile SDK. Any performance limitations you encounter are caused only by limits of device/OS you are using

2. i can't help with this specific question. but I doubt any alternative would help in this case, you need to debug deeper into performance issues you have with your UI

Mobile App Heap Size Issue – Investigation & Support Request

Chetan Ghaydar — Thu, 14 Aug 2025 05:07:02 GMT

We are experiencing an OutOfMemoryError in the SugarCRM mobile application, which appears to be related to the heap size allocation on certain devices. It is happening on certain events like page refresh, Menu item click after login etc.

Following SDK version we used for customizations

45.0.657-1.4.2

Quick Fix

Configuration added to AndroidManifest.xml: <application android:largeHeap="true" ... />

Impact:

Causes app crash, interrupting user workflows.

Affects specific devices more frequently, likely due to OS and hardware configuration.

Request:

Please advise on:

Any way to reduce heap size

Recommended heap size settings for SugarCRM mobile builds.

Any known SDK or configuration changes required to handle high-memory operations.

Possible workarounds to avoid crashes until a permanent fix is implemented.

RE: Mobile App Heap Size Issue – Investigation & Support Request

Chetan Ghaydar — Tue, 02 Sep 2025 05:47:42 GMT

Hi Eugene Bychkov We have checked all the scenarios. We found that we have very Complex & Heavy UI Frameworks. We also found that there is Heap size increase on locatoin.reload() we have used in our customization.

So we need help on following,

1. Is there any kind of limitation on customizations? like memory size etc.

2. Is there any alternate for location.reload()? which also applicable for custom filter @ run time.

RE: Mobile App Heap Size Issue – Investigation & Support Request

Chetan Ghaydar — Mon, 25 Aug 2025 11:36:07 GMT

Noted. Thanks for prompt reply. Will update the result.

RE: Mobile App Heap Size Issue – Investigation & Support Request

Eugene Bychkov — Mon, 25 Aug 2025 11:31:53 GMT

Hi Chetan
The size of these heap snapshots looks 'ok' to me

You could try disabling some modules from mobile to identify which module potentially overloads your device

After that you could try further investigation according to my earlier recommendations

Hope this helps and best regards

RE: Mobile App Heap Size Issue – Investigation & Support Request

Chetan Ghaydar — Mon, 25 Aug 2025 09:45:02 GMT

Eugene Bychkov Thanks for you ack of this issue and quick reply. Here We have got some screenshots of Heap snapshot. Would request you to suggest your recommendations based on this.