Genesys Cloud - Developer Community!

Hello Team,

we have the following technical questions regarding the Genesys iOS and Android SDKs as we begin our integration.

1. Interoperability with Objective-C? Our iOS Application uses legacy code, namely Objective-C, for most of core features. After installing the SDK, we have stumbled upon a couple compilation errors due to bridging Objective-C with Swift code.
2. Does Genesys provide a floating button to open the chat OOTB, or should this be implemented at a project level?
3. How are the Push notifications managed? On success / opening of the notification is there any payload for handling on the Applications?
4. Is Dark Mode supported by Genesys?
5. Does the Android SDK handle permissions at runtime?

Your guidance on these points would be greatly appreciated.

Thank you!

Mariano

Hi Mariano,

Thank you for contacting us. 

About your questions:

1. The SDK should work in Objective C host application smoothly. I would like to ask some questions for clarity:
   • I assume they used Cocoapods to install the SDK, is this right?
   • Which version of the SDK they are using?
   • Can we get the more details with the compilation problems?
2. No, the SDK does not provide any button to start the messaging, it should be implemented by the host application.
3. In the current implementation the payload only contains a keyword to detect, that the notification is coming from the messenger. The host application can start the messenger and the SDK will fetch the latest messages. 
4. No, unfortunately dark mode is not supported.
5. This question I need to confirm with the Android team. I will message here the answer.

I hope it helps.

Monika

Hi,

I got back the answer from Android team about the permissions:

We request for one permission inside SDK. When user wants to open camera, and permission is not granted, we request it. Displaying notifications is completely implemented on the app level, so even permission is handled there.

Monika

Thank you Monika!

All clear now

#1 was due to having same class and enum names as in the sdk, after renaming them the solution compiles successfully