With Heap Analytics is there a way of seeing which users have logged into an account? I mean logged into heapanalytics.com rather than the client facing app / website.
The UI doesn't offer a feature like this but if you reach out to support they can give you a report that will tell you who has logged in and when.
Related
I have implemented a login feature in my app where a user can pay for subscription and have that subscription tied to their in-app login account by using the setObfuscatedAccoundId() method. However, in a scenario where the current user(user_A) makes a purchase, logs out of the app and a different user_B logs in, user_B is unable to purchase the same subscription as it has already been bought by user_A (as they share the same underlying Google Play account) even though I DON'T want these in-app accounts to be related at all. Currently, what happens is user_B gets a responses that states "You already own this item". So that makes me wonder:
Can we actually possibly use a single/the same underlying Play Store account to purchase the same subscription while logging in to an app with different user accounts?
Also, what would be an ideal design approach for a problem like this considering the limitation?
I am still a beginner at this and would really appreciate your inputs!
I'm beginner at this like you and may I was wrong but I think you can not do that because the subscriptions are saved in your google account and you can not buy same subscription you owned already.
An internal script I use together with my research team uses the Drive API to automate file download from Drive. Some accounts, arbitrarily as far as I could tell, get the "temporarily disabled" message instead of the regular authorization screen.
The behavior is per account - some accounts always get the "temporarily disabled" screen, while the rest always get the desired auth screen. Switching accounts sometimes helps in case one's second account is in the "good group" that gets the auth screen.
We use #gmail accounts (not gsuite). The app uses the https://www.googleapis.com/auth/drive.readonly scope. The app has not been verified and I am aware of the cap when using sensitive scopes. It seems from the dashboard that we are below the user cap. Looking at OAuth consent screen > OAuth rate limits > Your user cap I see "5 users / 100 user cap".
Can someone explain this behavior?
Am I looking at the right thing on the dashboard?
Can I use a less sensitive scope that will not require verification? We only need to download specific files/folders.
If an app or service shows the Sign in with Google temporarily disabled for this app message it means that Google paralyzed the app/service for security reasons. The only thing that you can do is go through the verification process.
I received this message for the second time and i still dont understand why. Can someone help me?
Action required: Critical problem with your Google Cloud/API project
Youtube API (id: tonal-topic-123301)
Dear Developer, We have recently
detected that your Google Cloud/API project Youtube API (id:
tonal-topic-123301) is using a Google product name as the project name
shown to users on the OAuth consent screen, which violates the Google
API Services: User Data Policy. You can fix the problem by revising
the project name and other relevant content so that the OAuth consent
screen shown to users accurately reflects the identity of your
application. To revise the project name visible to users, please take
the following steps:
Please review the Google API Services: User Data Policy, specifically
the following section- "Do not make false or misleading statements
about any entities that have allegedly authorized or managed your
application. You must accurately represent the company, organization,
or other authority that manages your application. Making false
representations about client credentials to Google or Google users is
grounds for suspension."
Sign in to the Google Cloud Platform Console.
Select your project.
On the Home Page Dashboard, select Go to APIs overview under APIs.
In API manager, select Credentials on the left bar, then select OAuth
consent screen. Change the name in the field under Product name shown
to users and then click on Save. We will suspend your Cloud project in
3 days unless you correct the problem. Please submit an appeal if you
have any questions. Please note that you should be logged in as the
project owner to access the appeals page. For more help on submitting
an appeal or to learn more about the process check the Policy
Violation FAQ. Please take a moment to review the Google API Services:
User Data Policy, the Google API Terms of Service, the Google Cloud
Terms of Service and the applicable Terms of Service for the specific
Google API you are using so that you do not violate our terms and
policies in the future.
This is obviously a naming issue regarding something in the google product range.
You Should be able to re-name your project to solve this.
If not, try a Google forum or help pages.
The problem you are having is that Google does not allow you to use a Google product name as the name of your in your application. Users can become confused and assume your third party application was created by them.
How to fix it:
Go to Google Developer console find the credentials screen. Click on the Oauth consent screen tab at the top rename your application.
Note: If you don't do this google is going to shut down your application they are very picky about this.
I am working on an app in ruby using:koala:omniauth
When I click share to wall from the application it allows me to share and
changes my permission accordingly. When I use an account that is not setup as a developer it sends 200 error "permissions not provided." but does not ask for "permissions" like it did with the account connected to facebook developer.
Is there a setting somewhere on Facebook developer that controls this?
I would like all users to be re-asked the permission and not just developers of the app.
Yes, you need to ask Facebook to review the app for special permissions..
We have created an app on Yammer which is currently private.
We want to make it available and accessible to networks outside us. Please suggest if there is a way to get it authenticated by outside network or do we have to go by the process of submitting the app to Yammer support for global access.
If that is the case, please help us know how much time does it require to get reviewed and approved as it is almost a week and we have not heard back from Yammer support.
You need to submit the app to Yammer's App Directory for approval. Depending on your app you may also be able to allow users to configure their own Client ID, but this is really only a usable approach for developers or system admins. End users wouldn't understand how to do that.