I'm building an app and I don't know why (I've check a lot of post on StackOverflow and beyond) when I'm running the app on my iPhone through Xcode I've a message "Resetting plugins due to page load." and the device ID I need for push is not set or given and I'm not asked for push authorization. All of that work with a ionic tab starter project.
I've remove jQuery (for open links in the built-in browser of the device) and retry but nothing change... I've try to remove my AppCtrl who is load before the other view but nothing change. I haven't found solution on the web so far.
Thank for your help,
percypyan
Related
I have followed the set up doc of branch for react native io i.e. https://help.branch.io/developers-hub/docs/react-native
React native Branch io deep linking is working fine for Android part and For ios part if click the banner from my website it is taking me to appstore and not the app though app is installed in device.
When copy the link getting created when user clicking on the banner and pasting it in notepad and on long press I am getting "open in your app" option and its navigating to app.
Since the 'Open in your app' option is visible on long-pressing the link on Notes app, it means that the universal links are setup fine here.
As per your query in regards to the link being redirected to the AppStore even when the app is installed, occurs when the AASA files are not being fetched by the device. This is a common issue occurring in iOS (https://forums.developer.apple.com/thread/123554) as in when the device fails to fetch the AASA files but this is an intermittent one and can be fixed manually. Your device will also try to fetch the AASA files at certain durations so that might also solve the issue at times.
As for the manual process, would request you to check on the Branch documentation here and follow the necessary steps : https://help.branch.io/developers-hub/docs/ios-troubleshooting#section-validate-if-aasa-file-successfully-downloaded
If the console shows as the AASA files are not getting fetched, please try uninstalling the app, restarting the device, and reinstalling the app. Recreate the method of testing for AASA once more.
PLEASE NOTE : These steps are advisable only if the SDK is integrated fine as per our docs.
I've encountered a problem with deeplinks when testing them on several devices. I've found out that deeplinks works properly on ones of them(i.e. redirect to the app exactly) but on the others they redirect to AppStore.
I've read the Branch's troubleshooting guide about this issue(link below) saying that this problem may be caused by explicit prohibition of app links when pressing the button on the upper right corner of status bar.
And I've read that it can be fixed by long pressing the link from the Note app and then clicking "Open in App" button.
But the problem is that there is no such a button at all although the app is installed on device.
screenshot
P.s: I know that my universal links are fully configured and working because as I said deeplinks work properly on several devices and the same button(Open in App) appears in the Note app for these devices.
https://support.branch.io/support/solutions/articles/6000153326-ios-universal-links-troubleshooting-guide
I've found out the solution. When I add my URL scheme that I register on dashboard to my project's info.plist. I started being redirected correctly. But it didn't fix the issue with unemerging 'Open in app' button when long press link. And I cannot block app links. because there is no button in the status bar.
As for devices where deeplinks had worked initially they haven't broken. I still can block app links for these devices and 'Open in app' button appeares.
Amruta from Branch.io here:
If you are facing issues with Universal links configuration, our team has a validation tool that allows us to check various information about your Xcode project configuration to make sure everything is configured properly.
Once the configuration information is collected, the script sends it to Branch and returns a short-link you can follow to view the validation results. For exact instructions on running the script, I'd like to point you to the relevant docs page, found here:
https://dev.branch.io/getting-started/universal-linking-validator/
as well as the validator, which can be found here:
https://branch.io/resources/universal-links/
After running the local script, open the link in your web browser and enter your Branch Key and Secret to view the test results.
If you still continue to face issues I would suggest writing into integrations#branch.io and we'll walk through your integration with you!
I can't seem to find an answer to this seemingly simple question. I have an app that i've built using the command line phonegap tools and when i start this app it opens up. i am using something called ios_sim (https://github.com/phonegap/ios-sim) which launches the app in the simulator and does not launch xCode (i don't quite understand why this is a feature, it seems like xCode has some useful tools)
Anyhow, my app is not functioning the same way that it does in the browser and i need to debug it. I have also already installed Charles to inspect the requests and i can verify that the correct data is coming from my API so my assumption is that there is some sort of javascript error in rendering the page (the page is partially rendered btw).
All i want to do is view the javascript errors. the same way that you would in the console if you were looking at a web page.
how do you do that?
You have to use Safari Remote Debugging with Web Inspector. See in the relating cordova docs how to do that!
I'm having a very strange issue with my web app (which is ran in full-screen mode from the home screen) and Mobile Safari. Usually, as I develop, I edit the files with the changes that I want to make and then I re-launch the app from the homescreen. As per iOS design, the web app will refresh and reload the site.
However, in some odd but frequent situations, when I launch the application I get a cached older version of the app. If I navigate to the app through Mobile Safari (not from home screen) then everything looks great.
I've added meta no cache tags all over the space and even attempted to thwart the cache by adding ?query strings to .css files, etc, but for some odd reason when a cached version decides it wants to display - it will display, no matter what. Clearing cache and data from the settings menu and then relaunching will only sometimes fix the problem.
Anyone else run into this issue? If so, how did you fix it? Is it a known iOS bug? I'm thinking about adding some onLoad code to check if the application is running in full screen mode and then explicitly force a refresh.
Please help - this is extremely annoying and frustrating!
Rich
In my own testing I also found that applications run from the "Home Screen" on iOS won't properly refresh their CSS and JS files. This appears to be an ongoing problem. The only solution that worked for me was to:
Change the device date forward by 2 days or so..
Reload the app from the Home Screen..
Reset the date.
I also tried deleting and recreating the icon from the home screen and clearing the cache in Safari.
"Happily" you are not the only one seeing this problem.
https://discussions.apple.com/thread/3385843?start=90&tstart=0
Incase anyone asks. There were no manifest files involved in my testing.
iPad 2 with IOS 5.1.1.
Enable Debug console from "Settings>Safari>advance" and see if you've any errors there.
Most probably you may have an 'Invalid MIME type", Manifest Parsing or Resource Fetch Failure Error.
Fix them (this link might help in fixing those http://www.fuckyeahtml5.com/2011/06/debugging-html5s-offline-web-apps/).
I've been doing lots of work in getting a few web apps to work offline on iOS using the HTML5 manifest. I've ran across the typical problems everyone else has and fixed them and everything seems to be working fine—except in the case where I save the web app to the desktop on my iPhone 4.
If I do this and then enable airplane mode, I get the following alert when trying to access the app via the home screen: "your-app-name could not be opened because its not connected to the internet." Accessing the app via Safari browser works fine while offline.
If anyone knows if this is an error on my part, or even the slim possibility of a work around, do tell.
Even downloading the new Financial Times web app (very well done with extensive localStorage support) results in an error when accessing it offline from the home screen.
Technical specs: Running iPhone 4 with iOS 4.3.3 (but also saw the issue in 4.3.2)
After reading the comments (especially Rowan's) I ran more tests and found the answer:
No, Apple did not disable HTML5 offline capability for web apps saved to the home screen, it works - for the most part. There is a bug that will make it not work. It doesn't seem to have anything to do with your manifest setup (unless perhaps it downloaded a bad manifest or incomplete manifest at one point.) We don't know how widespread it is but the fix is to clear your Mobile Safari Cache.
Here's the steps:
Close the web app (make sure its not sticking around in the background).
Cleared Mobile Safari cache: Settings > Safari > Clear Cache
Reopened the app (for caching).
Close the web app again (make sure its not sticking around in the background).
Enabled "Airplane Mode": Settings > Airplane Mode
Reopened the app.
It should now work offline. If it doesn't then its probably a separate manifest issue in your app. Looks like a weird bug with the browser cache - or perhaps the cache was completely full? Who knows, but that's the answer. Thanks guys.
iOS seems to be very sensitive to load issues when offline.
I was getting your "could not be opened" error when offline on a page I was working on. The problem turned out to be that the page created an iframe pointing to a site that didn't have an AppCache. Removing those iframes fixed the issue.
In my case, I handled it using window.navigator.standalone which tells you whether you're running in an iOS homescreen app. The code looked like this:
if (!navigator.standalone) insertFrames();
add this to your html:
https://web.archive.org/web/20170201180939/https://jonathanstark.com/blog/debugging-html-5-offline-application-cache?filename=2009/09/27/debugging-html-5-offline-application-cache/
I found it massively useful - even though I've created my manifest file and compared it to other people's manifests this JavaScript debugging script gave me the clue I would have never found otherwise. I apparently had syntax error in my manifest ... long story short I had to remove everything and add the paths to each file/image one by one. The end result was the same however it worked... how weird!!! does whitespace / comments affect the syntax of the file?