I'm trying to add Firebase to an existing google project. Basically I want to migrate the project to Firebase.
Steps that I followed
Go to console.firebase.gooogle.com
Click import google project
Select the project (I have owner permission, but I didn't create the project)
Select the country
Add firebase
I get the following error:
Invalid entry. Please make sure you represent your app accurately.
Until today I was getting a generic error such "An error happened, try again", but this has changed.
When I check the browser console for the error, the status code is 400.
Is there anyone who had the same issue and resolved it somehow?
Note that I tried the following options:
Different accounts
Different browsers
Incognito mode
Clear cache / Disable add-ons etc
Clearly logout/login again
Nothing worked so far and this blocks me to proceed.
It turns out the error was referring the name wasn't proper in Google console. It was something like "Foo bar bar". Nothing special though. I got support from Firebase and changing name something "foo-bar" solved the problem.
To be honest the error message is too vague. Hopefully this helps someone else.
Related
all. I am trying to set up boxr to read files from Box's API.
The set up seems pretty simple. I created a Box app. I then copy/pasted the client secret and client ID into box_auth()
library(boxr)
box_auth(client_id = "<placeholder>", client_secret = "<placeholder>")
When I do this I am taken to a new page that says:
There seems to be a problem with this app.
Error: redirect_uri_mismatch
Because there are so few steps, I am a little lost on what could be going wrong.
Advice is appreciated.
Ran into this same issue after months of boxr working as expected - the steps and explanation outlined here resolved the issue on my end.
Going to the dev console for your Box account, and then to the "Configuration" tab, add http://localhost:1410/ as a Redirect URI:
Setup:
having a firebase project with crashlytics active
receive mails for crashes
try to open the crash from the link within the mail
Example link: https://console.firebase.google.com/project/xxx-8c64/crashlytics/app/android:com.example.project/issues/3fgdfgfdg9e86f653d84df9fdfdfdf3?time=last-seven-days
I have multiple accounts in chrome. One is my private, one is my work account.
My main account is the private one. (/u/0)
Now, once I try to open the link
result: get redirected to wrong user https://console.firebase.google.com/u/0/
expected result: asking which account I want to use to open the link
My current workaround is to stop loading the link in the middle and replacing the u/0 with u/1 and let chrome continue. This will load the link correctly. But it will not always work and is super cumbersome.
Is there anything I can do? Do some of you face the same problem?
(Besides logging in with my work account. No - I don't want to log out from my main and switch forth and back all the time)
Okay I found a way, although I would love to hear a better one.
Using a redirect chrome extension. Redirector
github Link
Chrome Extension Link
RegEx:
From: ^https://console\.firebase\.google\.com/u/./(.*)
to: https://console.firebase.google.com/u/1/$1
I'm trying to set up my dynamic link domain to use in Facebook Login with Firebase, and according to the docs, as stated in this question: Dynamic Links domain not available, it says that the domain should look like app_code.app.goo.gl.
However, when I follow the steps to do so, the domain always comes as https://custom_link.page.link and it doesn't work in the cordova build
(After placing the dynamic link domain, the build always returns this error: UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'manifest' of undefined and if I remove the link, it works again)
I don't know if it's related, but all of the tutorials and guides that I've checked always use the dynamic link domain as app_code.app.goo.gl
Sorry for the confusion - we just launched the page.link domain, so some of the documentation is still catching up. Everything else should look the same after that, so the main thing is to make sure that your app is set up to handle the domain you have for your links - in this case the page.link one.
I have a problem when placing an App module(v 8.4.8) on a page. When I placed an App module on a page I got a pop up saying "Had an error talking to the server (status 404). if you are an advanced user you can learn more about what went wrong - discover how on 2sxc.org/help?tag=debug".
This error happens on whatever action I try to do: trying to add and app, refresh page etc.
I checked a communication to the server using Firebug and seems that one of APIs are missing:
~/desktopmodules/2sxc/api/view/Module/GetSelectableApps
Referer: ~/desktopmodules/tosic_sexycontent/dist/dnn/ui.html?sxcver=8.4.8.19191
Did I missed something? Should I make some configuration after SexyContent module install (v 8.4.8)?
I just checked a video by Daniel Mettler where he showed how to install a module and seems that process is simple. Nothing to worry about.
Does anybody has any idea what might went wrong here?
The same actually happens when I install and Content module: Error about missing APIs:
~/desktopmodules/2sxc/api/view/Module/GetSelectableContentTypes
~/desktopmodules/2sxc/api/view/Module/GetSelectableTemplates
Thanks a lot for your time
My best guess is that it's an issue with the dnn domain/path configuration. So basically my guess is that
you have multiple domains, and if this is configured incorrectly, the paths in the js-calls won't fully match the original one
you have sub-portal (with paths like /products/) or something, and this isn't configured correctly in dnn
languages in portal-paths are causing similar issues.
So please compare EXACTLY the full base path and see if that's the issue.
I have been writing my own meteor accounts package and I seem to be missing something. I am not getting any errors in the browser or in the terminal so it's difficult for me to troubleshoot. The only error I get is from the accounts-ui package itself which is saying 'No login services configured.' The code can be seen at https://github.com/khamoud/meteor-accounts-stripe if anyone could take a look. Thanks in advance.
I created a accounts package myself a while ago and my advice would be to stick to whatever is done in the base accounts packages of the same service (in this case OAuth 2 it looks like) as closely as possible. I can see you have done that but there are minor differences.
I downloaded your package and tried it out myself. While I can't get it working (I haven't used the Stripe API so I wont be digging into it completely) I think I can make more progress than you have had.
First of all I don't get a 'No login services configured' error. Did you add your package? I did 'meteor add accounts-ui', created a packages folder in the my project's root and pasted your package folder into it, renamed it 'accounts-stripe' and did 'meteor add accounts-stripe'.
I then added a {{loginButtons}} helper to the page. With this I got the configure Stripe login buttons but it wouldn't open a pop-up when I clicked on it. I got an error message in the js console 'Uncaught Error: Duplicate service: stripe'. The problem seems to be you have the line:
Accounts.oauth.registerService('stripe');
in both accounts_stripe.js and stripe_client.js. Removing it from stripe_client.js fixed it for me. I could then add my API keys from stripe.
The next problem is once these are submitted you store them in 'clientId' in stripe_configure.js but then retrieve them using appId from the config object in stripe_client.js and stripe_server.js. I noticed this because the login URL in the pop-up after submitting the API keys had a undefined client_id. Changing 'clientId' to 'appId' in stripe_configure.js will fix that.
Unfortunately it still doesn't work. I get
{"error":{"message":"No application matches the supplied client identifier"}}
from the pop-up window. This could be for any number of reasons, perhaps I submitted the wrong thing in the API keys window, maybe it's because I'm using a test project on Stripe, or maybe you have implemented the login workflow incorrectly. A quick google of the Stripe OAuth docs suggests that I have submitted the wrong things for the client_id and secret. Like I said I haven't used the Stripe API before.
I hope I have got you started on fixing it though.