-
Notifications
You must be signed in to change notification settings - Fork 31
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
Receiving warnings about ending background task #21
Comments
This is a known bug of that library version, we would recommend that you update to the latest one. You can do that by modifying your |
The pod wouldn't update because you increased the minimum deployment level from iOS6, unfortunately cocoapods would just fail silently until I manually set the tag. |
That's correct, our minimum supported version is iOS 8. Whilst we did nothing that would prevent earlier versions from working, we do not test under those versions, so we can not tell whether they work properly there. |
Oh ok, I might have to work out how to override the minimum deployment
level with a pod post processing script
…On Thu., 29 Dec. 2016, 8:06 pm Jordi Giménez Gámez, < ***@***.***> wrote:
That's correct, our minimum supported version nos is iOS 8. Whilst we did
nothing that would prevent earlier versions from working, we do not test
under those versions, so we can not tell whether they work properly there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAW7-sqD-C9z7YmlnkbV1ZKtrwWF4T2qks5rM4YRgaJpZM4LWsWe>
.
|
I receive this message from the bugfender sdk framework:
Can't endBackgroundTask: no background task exists with identifier 16fd8a1a0, or it may have already been ended. Break in UIApplicationEndBackgroundTaskError() to debug.
I'm currently using 0.3.18 and not sure how to update the pod to the latest release... will I have to update the pod using the latest tag? Not sure if you've fixed this warning yet either :)
The text was updated successfully, but these errors were encountered: