Unhandled Rejection (Error): internal about sparkle HOT 4 OPEN

I thought it might have been because I was present in the same browser from multiple tabs under different users - one in this local devel instance and another on ohbm.sparkle.space/in/seasig .

@yarikoptic From memory I don't think I have noticed/seen this come up before even when i've been using both the local + deployed version at the same time.

I went to Home in the official one but issue persisted. I have not observed it in the official one.

@yarikoptic As noted at the bottom of the snippet you shared:

This screen is visible only in development. It will not appear if the app crashes in production.
Open your browser’s developer console to further inspect this error. Click the 'X' or hit ESC to dismiss this message.

So you're not going to see the same 'obvious pop up error' in the production environments. Though you will likely be able to observe the error in the DevTools JS console if it occurs.

Unhandled Rejection (Error): internal
new HttpsErrorImpl

@yarikoptic I believe HttpsError and internal tend to related to errors happening in the backend firebase functions, rather than the frontend code. So you may be able to get better details about it by:

• Looking in the firebase web/admin console
• 'Functions' on the left hand menu
  • 
• 'Logs' tab, then filter by 'Error'
  • 

I just had a quick look at env/ohbm and there didn't seem to be any error logs showing there for the production backend functions.

from sparkle.

I just ran into the same issue while trying to dev on this locally! This is the output of the error I see in the JS console. (I also didn't set up a Twilio token, as that was marked optional in the setup docs, but I'll try that out.) I think that's unrelated actually...maybe it's just the CORS problem?

from sparkle.

@talum When you see this CORS issue, are you running the firebase functions emulator locally? The main times I've seen CORS issues from the backend functions has been when not running the functions emulator (or when I have been running it, but had it mapped through to a different/wrong environment (than what my ENV files were pointing to) with firebase use)

• https://github.com/sparkletown/sparkle/blob/staging/docs/getting-started.md#launch-application

You're going to need 2 terminal tabs to launch Sparkle application locally. Make sure that you're located in the application root folder and follow steps below:

Run npm run firebase:emulate-functions in the first tab
Run npm run start in the second

And if you haven't already, the npx firebase login and npx firebase use PROJECT-ID parts of this:

• https://github.com/sparkletown/sparkle/blob/staging/docs/bootstrap-application.md#connect-your-application-to-firebase

from sparkle.

@0xdevalias Yup, I was running the firebase functions locally. It might be because I was running the firebase emulator with the firebase project I had created, while also using the credentials y'all had provided for the hackathon. That seems wild, I know. It was mostly to get around having to set up billing under the firebase account I had created.

Anyway, this is probably just good to know for whatever hackathons people might host in the future.

from sparkle.