Skip to content

Unhandled promise rejection: ReferenceError: Can't find variable: indexedDB #1552

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
tiavina-mika opened this issue Sep 17, 2022 · 2 comments · Fixed by #1569
Closed
4 tasks done

Unhandled promise rejection: ReferenceError: Can't find variable: indexedDB #1552

tiavina-mika opened this issue Sep 17, 2022 · 2 comments · Fixed by #1569
Labels
type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@tiavina-mika
Copy link

tiavina-mika commented Sep 17, 2022

New Issue Checklist

Issue Description

In React Native projet, I got this error when initializing parse.

Steps to reproduce


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

Parse.setAsyncStorage(AsyncStorage);
Parse.initialize('my-app);
Parse.serverURL = 'http://localhost:8085/parse';

Actual Outcome

Unhandled promise rejection: ReferenceError: Can't find variable: indexedDB

Expected Outcome

No errors and warnings

Environment

Server

  • Parse Server version: 5.2.4
  • Operating system: Windows 10
  • Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Local

Database

  • System (MongoDB or Postgres): MongoDB
  • Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): Local

Client

  • Parse JS SDK version: 3.4.4

Logs

[Unhandled promise rejection: ReferenceError: Can't find variable: indexedDB] at node_modules\idb-keyval\dist\compat.cjs:35:27 in safariFix__default._default.then$argument_0 at node_modules\promise\setimmediate\core.js:37:13 in tryCallOne at node_modules\promise\setimmediate\core.js:123:24 in setImmediate$argument_0 at node_modules\react-native\Libraries\Core\Timers\JSTimers.js:248:12 in _allocateCallback$argument_0 at node_modules\react-native\Libraries\Core\Timers\JSTimers.js:112:14 in _callTimer at node_modules\react-native\Libraries\Core\Timers\JSTimers.js:162:14 in _callReactNativeMicrotasksPass at node_modules\react-native\Libraries\Core\Timers\JSTimers.js:413:41 in callReactNativeMicrotasks at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:391:6 in __callReactNativeMicrotasks at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:133:6 in __guard$argument_0 at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:368:10 in __guardat node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:132:4 in flushedQueue

@parse-github-assistant
Copy link

parse-github-assistant bot commented Sep 17, 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 Sep 17, 2022
@mortenmo
Copy link
Contributor

I see this as well.. my ParseJS version is 3.4.1

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
3 participants