Xamarin InAppBilling - xamarin

I have a xamarin application with in app billing feature using the nuget package from James Montenegro. When user is uses the app for the first time, after a few hours, the user access to the app pages should be blocked
For example using is in page 1, after a some minutes or an hour, a page should be displayed to the user automatically with a button for user to pay to continue using the app. When user quit and reopen the app, the page asking user to pay should still be displayed if user haven't subscribed. Can you help me with this please. Thanks

Related

How to switch from multiple Google OAuth consent screen to single page

Our company has changed to a new google account due to rebranding. We've created new project, OAuth consent screen and a client. Since then, our users presented with, what I call, multiple consent screen. They have to click on every single permission popup separately and then submit the summary page This is annoying. Previously, there was one page with all the scopes/permissions on it only. Examples attached:
Before:
After:
Does anybody know what's going on and how to switch it back?
Thank you
There was an announcement from Google. It's the change they made.
https://developers.googleblog.com/2018/10/more-granular-google-account.html
We will show each permission that an app requests one at a time, within its own dialog, instead of presenting all permissions in a single dialog*. Users will have the ability to grant or deny permissions individually.

Domain app being rejected for not implementing SSO

We are an existing web application where schools are subscriptions and students under that school can use our web app. They currently have logins with projects under the logins.
Since students keep forgetting logins, schools want to start migrating to Google Apps marketplace app approach where all students have to do is click on universal navigation icon.
But since the students could already have an account with us, the first time they login from universal icon, they are provided with a screen to map any existing account or create a new one. Once that is done, next time the student comes in, they login and enter the app right away. No intermediate steps.
With that background, our marketplace app is being rejected with the reason, we do not implement SSO.
Can somebody help me understand how are we not implementing SSO?
It was an issue with mismatch credentials in the marketplace app and PHP code.
Used the same API keys in both places fixed it.

Do we need to wait after an admin accepts an app marketplace scopes for his domain in order to avoid consent screen?

We are integrating our app in the new Google Marketplace.
Our marketplace config in the developer console is ok.
Our oauth2/sso flow is ok (scopes match the ones setup in the console, auth params ok)
All users, when accessing our application through the Navigation bar, don't see any consent screen. All is perfect … except the following :
when an admin user is installing our application for his domain for the first time, he is presented with the domain consent screen displaying the scopes defined in our marketplace config, which is fine, he accepts and is presented with a button "Launch app". This link hit our server and a redirection is made to google auth in order to get the email and profile of that user. The redirection happens quickly that the admin is presented with yet another consent screen displaying the exact same scopes … which is bad.
If we wait 10 - 20 seconds before clicking the 'Launch app' button and after having accepted the scopes for the domain, the redirection to google auth is done and no consent screen is presented to the admin.
Are we missing something? Some sort of pooling technique with callback? "Sleeping"?
The same happens with other apps available on Google Apps Marketplace.
I installed several apps from Marketplace (Mavenlink, Lucidchart, etc), and they showed exactly the same result. I was prompted with consent screen immediately after installing them. A bit later, and I was let in without prompting.
It seems that the information on the installed app is not immediately propagated through Google system. There is a short delay between the time the administrator installs an app to his domain, and the time that app becomes available on his domain.
Most users wouldn't mind to wait a minute after the installation. Unfortunately, a reviewer at Google is not that forgiving. If he is quick enough to start your app immediately after the installation, your app will be caught asking for consent, for which it will be rejected from Marketplace. Too bad.

Why can't my client through his login update the calendar on his page that we created for him via Joomla?

We are having some trouble with a website we recently developed for a client of ours. He is a DJ. For his page, we added a tab that contains a calendar where he can post his events.
Using the admin login, I can successfully post events. However, the client (the DJ) cannot. When I tried using his login, I could not enter events either. Even stranger, I gave the client the admin login (which I used successfully) and he still couldn't post events! I even walked him through it, and he followed the same instructions, but no luck.
We can't figure this out. Here is the site in case it helps to review it.
Make the DJ's account a "super user" OR if you are using Joomla 2.5 or 3.0 you can change the permissions to give his user type access to the calendar.
Good luck!

How to avoid the login_sucess.html?

How can one avoid to have to show this redirect_uri = "https://www.facebook.com/connect/login_success.html" each time you login with your WP7 app.
I have a share button in my app which should post content to the facebook page of the user that logged in. Currently when a user already has entered username/password they still get to see the white screen "login_success.html" first and then the item gets posted and it returns back to the app page.
How can you avoid this screen in the app flow ?
I am using the facebook sdk C# v6...
Thanks.
You can make your browser control invisible after you got the access tokens

Resources