In our codebase library, we configure the NSTimeZone local time zone to the rollout-specific time zone because our apps relate to specific geo-locations (i.e. Nottingham area)
This setting is used to determine the timezone during the application's runtime. For the N&D rollout, we provide the value of Europe/London.
It appears that the Genesys SDK relies on the default NSTimeZone to determine if the support messages are unique or something similar. However, when we override this value, it breaks their internal logic.
If the default value of NSTimeZone isn't changed, the SDK works correctly and doesn't crash.
Are there any known steps to replicate the issue?: This issue is also reproducible in their sample app (referenced here: https://github.com/MyPureCloud/mobiledx-samples-ios). By simply overriding the NSTimeZone with any value, such as Europe/London, we can reproduce the issue.
Has this issue happened before? (If you have logged with Sabio previously, please provide the reference): This is related to a previous ticket raised ref: CINC0167517
Additional Information: This is an SDK bug because our app is using a valid iOS feature to set its own time zone, and no SDK should crash just because this value changes. The Genesys SDK incorrectly assumes the default time zone will always remain untouched, and its internal logic breaks when that assumption is wrong. Since the issue appears even in their own sample app when the time zone is overridden, it's clear the problem lies in the SDK, not in our implementation.
#Platform SDK
------------------------------
Gert Sogaard
Senior Consultant
------------------------------