I have integrated Firebase Dynamics Links into my app (using <myapp>.page.link domain) and it's all working fine. However, I have now found that in my login and registration screens I get username/password autofill appearing for website page.link. I'm not currently using autofill, and don't have the webcredentials entitlement, so this is very strange. Has anyone else come across this and know how to prevent it?
I'm seeing it every time for each new project with dynamic links.
I think that firebase's apple-app-site-association posted at <yourapp>.page.link is the only credible source of info it can find (even though it doesn't have webcredentials). Basically it looks like after failing to find webcredentials anywhere it falls back to the only available file with applinks.
The easiest way to prevent this is to take initiative from firebase and post own apple-app-site-association file with webcredentials at your site (with proper "webcredentials:<your.domain>" counterpart added into the Associated Domains capability).
Related
I made an iOS app (Swift) that signs in with Google, then fetches classroom data from the (Google Classroom API) https://developers.google.com/classroom. Everything was working correctly, and then some time later I think I accidentally deleted the Google Cloud project associated with it. So I had to re-create it and recreate an OAuth Client ID (I followed this guide on Google's website).
Now I'm getting an https status code 403 error - Permission Denied while trying to fetch classes, and I have no idea why. Does anyone know how to resolve this?
I believe the specific error (according to the Google Classroom API error section, linked above) is:
...but I'm very confused what to do to fix this.
One thing that is interesting is when I created an OAuth Client ID and downloaded the credential.plist (or credentials - can't remember) file and inserted it into the Xcode project, I get the same error as when the .plist file is not there. I'm wondering if I have it named something incorrectly? (Because before I had an entire GoogleService-Info.plist file since I had an associated Firebase project), but now that I don't need the firebase project anymore, I just have the credentials in the downloaded plist file which inherently is called credentials.plist.
Edit One strange thing is that I am only trying to read data, so I don't know why it's telling me I attempted to modify data.
If you are using some of the API to manage the classwork from the students with the Classroom API, you could be affected by this alert:
This could be interpreted in a way that, all the CourseWork that was managed by the previous Client ID is basically linked to that Client ID. This also has been discussed over the public issue tracker when it comes to Classwork created from the normal UI and how it can be managed:
https://issuetracker.google.com/issues/67748271#comment8
I would suggest to also share some feedback for this feature request so it gets the attention it needs. I notice that features like this for Classroom have been approved and implemented due to the high amount of users utilizing Classroom, generally it was previously limited however it has since been getting great support.
I am trying to set-up universal links for an iOS app.
The Apple search validator keeps failing when I try to validate the file apple-app-site-association with error message:
Unable to parse that webpage URL. Try a different URL.
The file content is correct, I tried with already validated files from other websites but it seems the crawler fails to access the website generally.
The domain and website are hosted on a shared server at 1and1.com without SSL. The file is not signed.
Any idea why that is?
This is the "App Search API Validation Tool", not the "Universal Links Validation Tool" (which doesn't exist from Apple). The results from this tool have no connection to whether Universal Links work or not.
That said, you must have SSL in order for Universal Links to work. That is the number one requirement. If you can't/don't want to set this up, look at an external link hosting service like Firebase Dynamic Links or Branch.io (full disclosure: I'm on the Branch team)
In reference to "you must have SSL in order for Universal Links to work. That is the number one requirement." This is no longer a requirement.
If your app runs in iOS 9 or later and you use HTTPS to serve the apple-app-site-association file, you can create a plain text file that uses the application/json MIME type and you don’t need to sign it.
Trying to configure Universal Links for iOS 9. I am using Apple's validation tool:
https://search.developer.apple.com/appsearch-validation-tool/
Everything is passing except I get Action Required for Link to Application. The message is: "Could not extract required information for application links. Learn how to implement the recommended Universal Links." I have tried running the tool both from my desktop and from a device that I believe is properly configured. Universal Links are not working for me when I try them from Safari.
There is nothing in the linked documentation that explicitly explains what this required information might be.
What fixed it for me, is realizing that you must enter an actual URL in the validation tool, and not just the domain (root) >IF< your apple-app-site-association file specifies a sub-path.
In other words, if only part of your website redirects to an app, be sure to enter in the validation tool a URL that includes the subdomain!
[Spent all day figuring this out - LOL]
In my case the issue was with the '#' symbol in the link.
While apple-app-site-association file has the wild card to any "/?/foo/*" links, "/a/foo/bar" will pass while "/#/foo/bar" will not
I am including sign in via google functionality in my app, for which i had created oauth client id keys for both of my debug and release mode, but since everything was not working properly so, i thought of deleting and re-creating it again, so i deleted both the keys but now when i trying to create the new keys it gives me error as
Duplicate fingerprint
The fingerprint you specified is already used by an Android OAuth2 client ID in this project or another project
but i had deleted both the key's, i had tried all the solution that are already present in stack overflow, like going into the old console portal etc. but none is helping me out,please help me with the issue
Did you try to go to your API console and UNDELETE your old projects? When you delete a project in the API console, the oauth IDs associated with it seems to not get deleted with it. I undeleted every single one and went through them and removed all associated APIs. Once I cleared out the past projects, I re-deleted them and added the oauth again to my new/safe project and it was OK.
Your problem seems to be little different, so you can look for different solutions here, as it's a common problem:
https://code.google.com/p/google-plus-platform/issues/detail?id=554
I am an ios app developer. We have implemented a custom URL scheme 'my_app://section_name' or so where if the link is opened in the user's mobile browser, it will redirect the user to a specific section in the app.
We would like to be able to tweet these URLs and have users on their mobile device click on them to open up the app, however it just can click once
(when you click close , maybe you click wrong then you want to click it second but it does not work )
I hope this isn't too silly of a question. Thanks
Make sure to check the tweet body after it have been posted.
This may be due of an URL shortener, especially if the tweet is posted from the iOS 5 Twitter framework.
I'm having a similar issue with url schemes. We can include them in emails and text messages, and they highlight and work properly.
Unfortunately, when we do the same with a tweet, the iOS Twitter client fails to recognise the special URL scheme and so the user cannot tap on it to open our app.
Pretty big oversight, methinks. Anyone else had any joy including special URL scheme links in tweets?
A solution that you should consider involves not sharing the URI scheme directly, but rather creating a page on your web server to handle this. In fact, if you want to be able to share full URI schemes with paths, you're better off building a web server to dynamically generate a page with a URI scheme redirect.
This is a over-simplified representation of what we built at Branch. This includes some code to get you started though the web server will require a bit of setup not described here.
instead of testapp://some.data.here, you'll link to http://yoursite.com/hosted-redirect/some.data.here.
your server should listen at the route /hosted-redirect, grab some.data.here and build the following page (body here):
(source: derrrick.com)
So your server will have to generate and respond with this page, filling in some.data.here, anytime http://yoursite.com/hosted-redirect/some.data.here is requested.
A lightweight node app could do this with a single file.