Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iOS15 Crash with isLowPowerModeEnabled #227

Closed
pBoelck opened this issue Oct 5, 2021 · 6 comments
Closed

iOS15 Crash with isLowPowerModeEnabled #227

pBoelck opened this issue Oct 5, 2021 · 6 comments

Comments

@pBoelck
Copy link

pBoelck commented Oct 5, 2021

image

TealiumSwift SwiftPackage Version:
2.4.4

OS Version:
iOS 15.0

Deployment Target:
iOS 11, iPhone + iPad

Suggestion to fix this problem:
DataDog/dd-sdk-ios#613

@craigrouse craigrouse transferred this issue from Tealium/tealium-ios Oct 5, 2021
@craigrouse
Copy link
Contributor

@pBoelck There is a fix available for this in the latest release. Please upgrade, and set the config flag config.batterySaverEnabled = false, which will prevent Tealium from registering for the low power notification. Unfortunately this is the only solution until Apple fixes the bug in iOS 15.

@pBoelck
Copy link
Author

pBoelck commented Oct 5, 2021

Thank you for the timely response. 👍

@pBoelck pBoelck closed this as completed Oct 5, 2021
@craigrouse
Copy link
Contributor

@pBoelck You're very welcome. Please note that we've been unable to reproduce the crash in our testing, but we are confident the fix should work, as it avoids us registering for the notification at all.

@pBoelck
Copy link
Author

pBoelck commented Oct 5, 2021

@craigrouse We have been unable to reproduce the crash too.
Hopefully apple will fix the problem soon.

@pBoelck
Copy link
Author

pBoelck commented Oct 5, 2021

@craigrouse
One last question from my side.
The version 2.4.4 has the config setting config.batterySaverEnabled = false.

Is it still necessary to update to 2.4.6?

@craigrouse
Copy link
Contributor

@pBoelck yes - previously we still registered for the notification even with this setting set to false. Now we only register if it's set to true, so having it set to false should prevent the crash, but only in the latest release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants