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

firebase 10.24.0 crash #12859

Closed
iOSyifeng opened this issue Apr 28, 2024 · 3 comments
Closed

firebase 10.24.0 crash #12859

iOSyifeng opened this issue Apr 28, 2024 · 3 comments
Assignees

Comments

@iOSyifeng
Copy link

Description

[NSConcreteFileHandle writeData:]: No space left on device
__90-[FIRCLSRolloutsPersistenceManager updateRolloutsStateToPersistenceWithRollouts:reportID:]_block_invoke (FIRCLSRolloutsPersistenceManager.m:63)

Reproducing the issue

No response

Firebase SDK Version

10.24.0

Xcode Version

15.3

Installation Method

CocoaPods

Firebase Product(s)

Remote Config

Targeted Platforms

iOS

Relevant Log Output

[NSConcreteFileHandle writeData:]: No space left on device
__90-[FIRCLSRolloutsPersistenceManager updateRolloutsStateToPersistenceWithRollouts:reportID:]_block_invoke (FIRCLSRolloutsPersistenceManager.m:63)

If using Swift Package Manager, the project's Package.resolved

[NSConcreteFileHandle writeData:]: No space left on device
__90-[FIRCLSRolloutsPersistenceManager updateRolloutsStateToPersistenceWithRollouts:reportID:]_block_invoke (FIRCLSRolloutsPersistenceManager.m:63)

If using CocoaPods, the project's Podfile.lock

[NSConcreteFileHandle writeData:]: No space left on device
__90-[FIRCLSRolloutsPersistenceManager updateRolloutsStateToPersistenceWithRollouts:reportID:]_block_invoke (FIRCLSRolloutsPersistenceManager.m:63)

@google-oss-bot
Copy link

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

@paulb777
Copy link
Member

Based on the error message, the device was out of space. We might be able to handle it more gracefully, but it's unlikely the app will be able to succeed.

@paulb777
Copy link
Member

The fix was merged from #12863 and will be in the 10.27.0 release.

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

No branches or pull requests

5 participants