-
Notifications
You must be signed in to change notification settings - Fork 40
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
Cannot access realm that has been closed (Sentry ID: 48099628b46440b298321f35de569601) #1227
Comments
Hi @lofimob - can you reproduce this consistently or is this just a one-time occurrence? If you can, what steps do you perform? Also - can you help me understand how this is "causing your users not to be able to use your application"? |
Consistently. Having errors even in Realm Studio. Several errors such as
Bad User Authentication, and Cannot access realm that has been closed.
Please help this instance is used in production.
…On Fri, Nov 22, 2019 at 11:08 PM Kræn Hansen ***@***.***> wrote:
Hi @lofimob <https://github.com/lofimob> - can you reproduce this
consistently or is this just a one-time occurrence? Also - can you help me
understand how this is "causing your users not to be able to use your
application"?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1227?email_source=notifications&email_token=AKXID7JS4H4MTHZYCW6IKOTQU7YWHA5CNFSM4JQRWAQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE542NA#issuecomment-557567284>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKXID7IRF6ZSVKYD4ZCOSN3QU7YWHANCNFSM4JQRWAQA>
.
|
Your production issues is likely not depending on Studio working, right? |
Not a bug in studio, my apps can’t access my instance. I believe my realm
instance is having problems
How do i create a support ticket
…On Fri, Nov 22, 2019 at 11:26 PM Brian Munkholm ***@***.***> wrote:
Your production issues is likely not depending on Studio working, right?
So you are trying to debug an issue with Realm Cloud?
If you are having a production issue with Realm Cloud, please create a
support ticket.
@lofimob <https://github.com/lofimob> Please describe your issue in
details with Studio here. But only if you think this is a bug in Studio.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1227?email_source=notifications&email_token=AKXID7NNLKFB3PT4L6FHIYDQU723FA5CNFSM4JQRWAQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE567VQ#issuecomment-557576150>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKXID7MVPITRZFJ6ZXIIQXLQU723FANCNFSM4JQRWAQA>
.
|
Take a look here: https://realm.io/support/ |
@kraenhansen I would still assume above message shouldn't be possible to get? |
I meant "Shouldn't" :-) |
➤ Unito Sync Bot commented: Transition made by Unito |
I'm having this issue on Realm Studio, hence causing my users not to be able to use my application.
Error: Cannot access realm that has been closed. at gt.componentWillUnmount (file:///Applications/Realm%20Studio.app/Contents/Resources/app.asar/build/server-administration.renderer.bundle.js:1:66970) at callComponentWillUnmountWithTimer (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:21863:12) at HTMLUnknownElement.callCallback (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:336:14) at HTMLUnknownElement.sentryWrapped (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/@sentry/browser/dist/index.js:3204:27) at Object.invokeGuardedCallbackDev (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:385:16) at invokeGuardedCallback (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:440:31) at safelyCallComponentWillUnmount (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:21870:5) at commitUnmount (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:22359:11) at commitNestedUnmounts (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:22453:5) at unmountHostComponents (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:22777:7) at commitDeletion (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:22863:5) at commitMutationEffects (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:25281:11) at HTMLUnknownElement.callCallback (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:336:14) at HTMLUnknownElement.sentryWrapped (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/@sentry/browser/dist/index.js:3204:27) at Object.invokeGuardedCallbackDev (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:385:16) at invokeGuardedCallback (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:440:31) at commitRootImpl (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:25008:9) at unstable_runWithPriority (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/scheduler/cjs/scheduler.development.js:818:12) at runWithPriority$2 (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:12130:10) at commitRoot (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:24889:3) at finishSyncRender (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:24296:3) at performSyncWorkOnRoot (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:24274:9) at /Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:12180:24 at unstable_runWithPriority (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/scheduler/cjs/scheduler.development.js:818:12) at runWithPriority$2 (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:12130:10) at flushSyncCallbackQueueImpl (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:12175:7) at flushSyncCallbackQueue (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:12163:3) at discreteUpdates$1 (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:24390:7) at discreteUpdates (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:1442:12) at dispatchDiscreteEvent (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/react-dom/cjs/react-dom.development.js:5885:3) at HTMLDocument.sentryWrapped (/Applications/Realm Studio.app/Contents/Resources/app.asar/node_modules/@sentry/browser/dist/index.js:3204:27)
This happened all of a sudden.
The text was updated successfully, but these errors were encountered: