Mapping and GIS Solutions Community

 View Only
Expand all | Collapse all

Integrating Catalyst SDK with Native Android Application

  Thread closed by the administrator, not accepting new replies.
  • 1.  Integrating Catalyst SDK with Native Android Application

    Posted 04-17-2018 04:44
    No replies, thread closed.

    We are building a native android application and would be using catalyst services for location data. Based on our reading through the technical documents provided by Trimble, we have integrated the Trimble Catalyst SDK with our application. During development we had few issues relating to 64 bit libraries which caused crashing of our application. And on removing them our application was working fine. We have tested in few different devices like Moto G5 Plus, Moto G4 Plus, Lenovo K7 Note on which the application was working fine. All these devices ran on Android 7.0 Version. In few devices like Redmi Note 4, Lenovo K6 which had android version 7.0, the catalyst service was not running when we initiated through our application but was running when testing through Trimble Mobile Manager. We request you to provide us some solution on making the application workable on all the devices. If there are any limitations/issues with any specific Android Device/ Version kindly let us know. Thanks for your time. Expecting a sooner reply.

  • 2.  Re: Integrating Catalyst SDK with Native Android Application
    Best Answer

    Posted 04-18-2018 02:44
    No replies, thread closed.

    Hi Sreetharan,


    we are not aware of issues with Redmi Note 4 etc in general - neither can I find anything related in the Play Store Console of either TMM or the Catalyst Service.

    So I don't believe/ hope its a generic issue.

    Could you please double check the permissions of the application you develop. The app needs access to the external SD Card - as the subscription gets read from there. Sometimes the switch in 'Settings' --> 'Apps' --> 'Permissions' is off although the manifest is correct and the runtime intent was sent.

    Plus - as the application is not registered so far - you need to test based on debug builds. Release builds will trigger an application finger print - which will fail currently.

    Another thing that might shed some light here are the logs collected by TMM. So if you open the Developer Gateway of TMM (details in the TMM dev docu) and enable logs as described there, then MINIMIZE TMM (so please don't kill it), ensure you are disconnected from Catalyst and try your app.

    After doing this 2 or 3 times there might be issues collected in the log.

    Keep in mind that TMM should not be connected to Catalyst during any testes as Catalyst is a 1:1 connection - so application to soft GNSS receiver.

    The devices that cause the problem are also not rooted or anything similar, or?