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
Related
I have activated free Google cloud account giving me access to the google-geocoding-api key of limit up to $300.
How do I know that how much my application is accessing the api per day and how much is remaining? Is there an option for displaying how much I have access the API over time or possibly a notification that will be sent to me.
I want to know about the calculation of key access per day and the daily usage limit. From where I can see these details.
Thank you.
You should get an email every month starting how much you have used that month and what you are being billed.
you can also check your Google developers console and see the current status of your billing account.
If you check the quote section you will find details on what calls you have made to the API and their response codes
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.
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
When developing bot for Telegram is there any way to get user timezone? Date field in Message object contains UNIX timestamp only. I want to create bot sending some messages an fixed time of day to subscribed user. User can have different time zones and I don't want to force users to explicit send their timezone to bot in message.
It's imposible by standard Bot API.
You can ask user for location, and next, from this location calculate timezone for user.
I've added /set_utc_offset command to my bot where users enter the time difference in minutes compared to UTC
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!