Skip to content

React Native (Parse JS API Issue) "Can't find variable: indexedDB" #1440

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

Closed
4 tasks done
chillaxdev opened this issue Jan 11, 2022 · 5 comments
Closed
4 tasks done

React Native (Parse JS API Issue) "Can't find variable: indexedDB" #1440

chillaxdev opened this issue Jan 11, 2022 · 5 comments
Labels
type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@chillaxdev
Copy link

chillaxdev commented Jan 11, 2022

New Issue Checklist

Issue Description

In a react native project, attempting to set Parse async storage using JS API (setAsyncStorage) throws an error "Can't find variable: indexedDB". The Async Storage is from @react-native-async-storage/async-storage

Steps to reproduce

import AsyncStorage from '@react-native-async-storage/async-storage';

const Parse = require('parse/react-native.js');
Parse.setAsyncStorage(AsyncStorage);

I've reproduced the issue in this repository below with minimal code.
https://github.com/chillaxdev/RNIDbIssue

Actual Outcome

Possible Unhandled Promise Rejection (id: 0): ReferenceError: Can't find variable: indexedDB

Expected Outcome

No errors & warnings.

Environment

Client

  • Parse JS SDK version: 3.4.1

Logs

Issue

@parse-github-assistant
Copy link

parse-github-assistant bot commented Jan 11, 2022

Thanks for opening this issue!

  • 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

@mtrezza mtrezza added the type:bug Impaired feature or lacking behavior that is likely assumed label Jan 12, 2022
@ndukachukz
Copy link

Have you been able to fix this yet. If you have pls share how you did it.
I'm having thesame errors

@chillaxdev
Copy link
Author

@ndukachukz You can temporarily use version 3.4.0 to avoid this issue.

@tiavina-mika
Copy link

Is there a fix about this issue? It has been here for a while

@dplewis
Copy link
Member

dplewis commented Jan 27, 2023

Closing via #1569

@dplewis dplewis closed this as completed Jan 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Development

No branches or pull requests

5 participants