When visiting https://app.google.stackdriver.com I am presented with the error Unable to load the account list, reload and try again., then after ca. 2 seconds I'm redirected to the Stackdriver logo and a link Log in with Google. After clicking that and selecting my account, I am redirected to the beginning of this problem again.
When going to https://console.cloud.google.com and selecting Stackdriver in different projects, I am sent through erroneous the process.
This issue was solved by support after filing a bug with the details. The specifics of the problem weren't communicated.
Related
I just don't know what to do anymore. I have a React-Native app and I'm trying to use Firebase Analytics to log Events in the app. I'v followed the entire installation of https://rnfirebase.io/ and https://rnfirebase.io/analytics/usage. Having done that I'v tried to log an Event but I can't see it in Firebase.
What left me completely baffled is that activating the app for Debug View mode with -FIRDebugEnabled in XCode worked. I could send an Event on the app and see it on the Debug View console in Firebase. When I deactivated the Debug mode WITHOUT ANY CHANGE only -FIRDebugDisabled in XCode the app did not send any Events to the Events console. I don't get any error there is no way to know what is happening. I have no idea of what I need to do or how to fix it.
Maybe some configuration inside the GoogleServices-Info.plist? Something inside the Scheme in XCode?
What should I do?
EDIT: I´v read a lot of answers here. Just to clarify the Events names are not a problem (no spaces or more than 40 chars) and I´v filtered Today and all posibles filters.
Unlike the DebugView, Firebase doesn’t display data in real time. There’s an intended delay before the analytics data is logged on your Analytics dashboard. The initial data logged usually takes up to 24 hours to display and 3-4 hours delay for the succeeding data. For additional information about it, you can refer to this blog post.
5I'm creating a google actions for Google Home, i'm using dialogflow and firebase functions and database to create the all thing.
So far everything was working good together but yesterday an error occured that i dont understand.
When i want to test my agent on the Simulator section of Google Actions, the agent is not responding even if in the logs i can see that the response is actually received by the simulator as shown here
And it answer this in the simulator
The response is empty and i have this simple error in the Debug section
It worked perfectly before but i may have change one thing that crashed everything and i can't find it.
EDIT
As recommended by #Prisoner, i've checked the History to find this
So i checked the logs and i got this (after Dialogflow Request and Dialogflow fulfillment request who were looking good)
It seems that the Dialogflow fulfillement response is having problem with URL ???
EDIT2
My URL fulfillment (firebase functions) was wrong, now that i have changed it, the log in my History seems ok :
But i'm always getting the same error on the Simulator.
Your logs show that your fulfillment is not deployed correctly and the URL is pointing to a HTML 404 page. This will cause your app to stop responding.
You may be running into the recent "first TTS is not spoken" bug in the simulator. I suggest changing your surface to speaker instead of phone. You can read more about this here.
I copied the example given in Google Calendar API Quickstart and replaced it with the appropriate info. Every time I refresh the page, I'm asked to authorize before api data is fetched.
I'm using Chrome and I currently have multiple accounts / users. I noticed if I open an Incognito Window and sign in with one set of credentials then when I refresh the page I'm not asked to authorize.
Note, once I authenticate I receive calendar information so I don't believe it's an issue with client_id, api_key, scope, etc.
Looking at the example code, I'm guessing the getAuthInstance() is getting confused because of multiple accounts / users. Does anyone have any idea? Thanks!
This was happening when running on localhost. This issue stopped happening after deploying the webpage to a hosted server.
When I go to my site on mobile it almost instantly shows up as an active user on google analytics. But when I do so on PC it never shows up as an active user. Even tried going to the site through Rabb.it
Also it shows active users 1 but "no data has been received the last 48 hours", does it just take time to update?
Have you looked at the JS debugger on your PC browser? Maybe there is an error that is causing the script to load incorrectly?
I've seen Firefox block the actual HTTP request to the analytics tracker, for example if you have private browsing turned on. I would start with using either Chrome's Developer tools or Firefox in conjunction with Firebug to try to take a peek under the covers as to what is occurring, i.e.
Verify that the JS actually loads correctly
Check for debug errors on the JS console
Check to see if the HTTP request is actually going through.
If your browser is blocking it you will see something like the image below.
I'm developing a web application in php that uses CURL calls to Facebook Open Graph with an authorization token.
I'm implementing calls to follow action and it runs fine with the test users profiles, but it provokes an error message when it uses Open Graph Test User as a profile.
The message is the following:
{"error":{"message":"(#100) Could not resolve object at URL 100004155724366.","type":"OAuthException","code":100}}
This happened using both the Open Graph Test User as the follower and as the followed.
I find information about this bug here, but it doesn't solve the problem.
I receive reject messages from Facebook when I send it to Review because the Open Graph Test User fails, despite I let them know about this issue.
Is there a way to execute this follow action via CURL, using Open Graph Test User without errors?
I very much appreciate your help. This thing is getting me nuts.
I faced the same issue as you did and filed a bug with Facebook: https://developers.facebook.com/bugs/1509327415958565
Facebook was able to reproduce this issue and are mentioning it appears to be a bug and assigned this task to the appropriate team.
Edit:
It turns out this behavior is by design when a test user is following a real user. FB recommends for testing to use 2 test users and let one test user follow the other test user.