Reverting events changed with patch - google-calendar-api

I changes a users calendar with the patch command and removed notes they had written.
Is there a way to revert the calendar back to before the change?

Google does not store event history if you over wrote it and did not store it internally within your own system there is no way to get back the data

Related

Events not logged in firebase console

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.

GTM Consent Mode: Best way to trigger updateConsentState without full page reload?

Probably a real beginner question, as I'm trying to wrap my head around Google's architecture. I've written a custom sandbox template that is triggered by Consent Initialization - All Pages, as described in the official support document: https://developers.google.com/tag-platform/tag-manager/templates/consent-apis
Now, what I can easily do here is to set the default states and update them if the user had previously made a choice and I read out their consent from a cookie. I run the update through the callInWindow() function, which appears to be the only API function that's able to communicate with code outside of the sandbox through callback functions that I can grant access to.
Now for the following use case: The user pulls up my cookie banner and makes a different choice. If I continue using the default "Consent Initialization" trigger, then I'd be forced to make a full page reload so that the callInWindow() function runs once more in order to perform updateConsentState() with updated data from my website code.
I'd actually like to avoid the full page reload, cause that just feels somewhat clumsy from an end user perspective. Is there anything that speaks against calling my sandbox template with anything else than "Consent Initialization - all Pages"? I think I'd just create another trigger that responds to a specific button click to re-run my sandbox template and update consent through the callback function again. But nowhere in the code samples I see consent templates being used together with any other than aforementioned trigger. What I typically see is people using the dataLayer to push updates after user interaction, which Google says should not be used for consent-related settings.
Can I just go with my idea or is there anything that speaks against it?

Google Analytics User-ID-status showing as "Unassigned"

I have this scenario
I enabled User-ID feature and Session Unification feature.
On the frontend when someone Signup I set their newly created UserId and I trigger custom event, that says that someone signed up.
Then I trigger another custom event from the backend that say that user becomes a friend with someone (need to do this fro the backend) and I'm using Measurement Protocol for this hitting this endpoint when this happens https://www.google-analytics.com/collect?v=1&t=event&tid=trackingId&uid=uid&ec=eventCategory&ea=eventAction&el=eventLabel
Now the problem that I have is that I did a small test, where I registered 2 users, and for one I become a friend with someone just to see if that event triggers too
Inisde the Realtime everything works as expected, but when the reports show up the next day I got 1 user with status Unassigned
Any Ideas what can break this flow and how this can happen? I thought If data in realtime is ok that it will be on reports too, Thanks!
Miss & before ea parameter. This can make issue because event action will not recognized and it is a required parameter.
EDIT
if you have done the tests too far apart (30 minutes) you can generate some inconsistencies due to the session, considering that you send an event.
Note: real-time data is generally unreliable.

Authorizing the Google Calendar API in Zapier Code

I'm trying to write a Zap which will get events from a Google Calendar for the current week and generate a string describing when I'm in the office "Mon, Wed, Fri". The only thing that's stumping me is step 0. How do I auth for the Google Calendar API in a Zapier Code block? It appears that Google calendar only supports Oauth2.0 and only gives out short-lived tokens but I want this scheduled job to only run in the background and have no recourse for user-interaction. Is there any way to generate a long-lived access token?
David here, from the Zapier Platform team.
Unfortunately, that's not something that's easily doable. Part of what Zapier does for you is refresh the tokens and ensure everything is running as expected. Searching for a bunch of data (this week's events) isn't really in the zapier wheelhouse at this time.
If you're only concerned with new events, you could set up a "new event" trigger that adds the date of the event into Storage and a second zap that runs weekly, reads storage, figures out what dates are busy, and generates your string. That wouldn't hold up for recurring events though, so it may not be what you're looking for.
Alternatively, you could try and do the refresh loop in your code block, but that's really tough. You'd need somewhere to persist the token (while Storage technically works, it's open to the public so it's not a great place to store creds, even if they are hard to find). You could try your request, refresh if the token is stale, then send the eventually present value onto a later step.
Sorry I don't have better news. ​Let me know if you've got any other questions!

Subscribe to iCloud calendar on Google

I am trying to subscribe to an iCloud calendar on my Google calendar. I am really open to any methods, but here is the one that seems most likely to work. See instructions to build proxy calendar. The problems is that when I try to subscribe to this proxy calendar (using both webdav://... and _http://...), I get the error message "Settings Error--Could not fetch the url." I know the file should work because I was able to use it in Outlook. Any idea on how to fix this, or a completely different alternative that I have not found?
So, the problem fixed itself the next day. I assume this is because Google cached the error and was not going to bother fetching the calendar again. So I guess this was a non-issue.

Resources