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

fix: handle CursorWindowAllocationException #454

Conversation

1abhishekpandey
Copy link
Contributor

@1abhishekpandey 1abhishekpandey commented Jun 26, 2024

Description

Some users have reported that their app is crashing due to a CursorWindowAllocationException. This exception occurs when memory is not available. In this PR, we attempt to catch this exception.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist:

  • Version upgraded (project, README, gradle, podspec etc)
  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added unit tests for the code
  • I have made corresponding changes to the documentation

@1abhishekpandey 1abhishekpandey self-assigned this Jun 26, 2024
Copy link

sonarcloud bot commented Jun 27, 2024

@1abhishekpandey 1abhishekpandey marked this pull request as ready for review June 30, 2024 15:45
@1abhishekpandey 1abhishekpandey requested a review from a team as a code owner June 30, 2024 15:45
@1abhishekpandey 1abhishekpandey merged commit 5ddc570 into develop Jul 1, 2024
14 checks passed
@1abhishekpandey 1abhishekpandey deleted the fix/sdk-2062-handle-cursorwindowallocationexception-in-android branch July 1, 2024 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants