Currently I am using >3 version firebase SDK.
In the new api, auth.sendPasswordResetEmail sends a reset link in the mail which expires in 2-3 hours.
Is it possible to enable a 24 hour just like old version? and if so, how?
Unfortunately, it's not currently possible to set the expiration time for any of the generated email links. They don't publish the expiration times either. They said it about 1 hour.
Read more:
https://github.com/firebase/firebase-js-sdk/issues/1884
Related
What does Google Calendar's API use as a default expiration value for resource watches?
The GCal Node Client uses an expiration of 7 days when I don't pass it my own expiration value. Someone previously stated that the default is 7 days, and the max is 30 (here), but I haven't seen that verified in any official documentation.
Google Calendar API's Push Notification doc says that this expiration value for a resource watch is
determined either by your request or by any Google Calendar API internal limits or defaults (the more restrictive value is used)
...but I haven't found where this "internal limit or defaults" value is officially documented.
I'm looking for a more official answer, because I don't want to have to set an unnecessarily quick expiration or have my sync code break if Gcal changes their default values
As per the documentation on Events Watch:
params.ttl
string
The time-to-live in seconds for the notification channel. Default is 604800 seconds.
And as per Google:
NB: The same information can be found for Acl: watch, CalendarList: watch and Settings: watch.
i am facing an issue with app subscription based on expiry date on firestore. If admin set a specific expiry date against specific user. and in android, i need to compare the current date with expiry date. But here is a real time problem, if customer change the device date previous to current date. In that case i am unable to handle the expiration.
Has everyone experienced the same issue ??
Can someone help me out, how to handle this case ??
Thanks in advance
I'm using Firebase Analytics and User Properties in my app to collect some data and to see how the users are using the app etc.
My app has both Free Version and Pro version. Before hire the Pro version, the user can use the Pro Version as a Trial of 1 month. When the user starts the Free Trial, I'm creating a event named "started_free_trial" and with this event I'm sending a "created_at" event attribute equal to System.currentTimeInMillis().
Now I want to send the cloud notifications from the Firebase console to the users who are using the trial period of Pro version at intervals of 15 days, 25 days and 30 days from the free trial start.
So here are the points what i want to do exactly
Create a Audience of users who started the Trial 15, 25 and 30 days ago. Can I do that? As Firebase provides an option to create audiences but I don't know how to create such type of audience to filter according to my requirement.
I want to send notification to that above created audiences.
I need your help to complete/perform above 2 points.
Looking for positive response.
Thanks
You can't really create an audience based on time the user started using your app, since the audiences are sticky, once a user is in the audience she will remain there forever.
However, instead of targeting to an audience, you can use user property directly to target your notification to users that registered after certain time or before certain time.
Just make you app to store the first start time to user property and the use that as the condition. You can also create other relatewd conditions and combine them.
I'm trying to figure out an issue where the user's login timestamp are zero. Their created and access timestamps are both set correctly. What can cause this login timestamp to be set to zero? We recently updated our drupal core with latest bug fixes, could that cause the timestamp to be set back to zero? I tried search all over but couldn't find anything related to this.
The login timestamp will get set correctly again once the user logs in again. But there are some functionalities which relies on the timestamp to be set correctly and wanted to see how we can avoid this in future.
Thanks in advanced!
What's the rate limit of graph api?
I have done a lot of searching and asking on the web. Some said 600calls/600secs, but I did not manage to find the official decalration of rate-limiting issues.
How long does graph api's access token expire?
No being able to find it anywhere
This limit is not mentioned anywhere in the documents. This limit is user specific i.e If u are making 600 calls in 600 secs for 1 or more tokens of a user. There can be a workaround by using tokens of different Apps but same user, if u need to make so many calls.
1.I don't think there is any rate limit on the Graph API although they have some thresholds mentioned at Facebook Platform Policies stating
If you exceed, or plan to exceed, any of the following thresholds please contact us as you may be subject to additional terms: (>5M MAU) or (>100M API calls per day) or (>50M impressions per day).
2.The access token (and not extended access token) has validity of 60 mins. You can also query Facebook Token Debug API for the exact token expiration. Although Facebook mentions this short duration in a range of 1 to 2 hours here, which can be used to retrieve a extended access token with validity of 60 days.