[
https://issues.apache.org/jira/browse/CB-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341704#comment-14341704
]
Tom Cline commented on CB-7606:
-------------------------------
[~shazron]
Thanks for the patch! Unfortunately, I am still at a loss due to my ineptness
or a conflict. Through the CLI I removed the ios platform, removed the shareURL
plugin, and then proceeded to update cordova (4.2.0), add ios3.8 to the
project, re-add the shareURL plugin, prepare the project, and build the project.
Alas, I am now to a point where handleOpenURL never fires, cold or warm. I have
repeated this process a few different times, in different sequences to the same
end result. Any possible ideas where the conflict/issue could reside?
I am also using, if it helps the following plugins (and have tested without
wkwebview just to be safe, with the next steps being of testing on an empty
project):
device
wkwebview
media
file
socialsharing
statusbar
splashscreen
inappbrowser
Thanks for any help or direction you may be able to offer.
> handleOpenURL handler firing more than necessary
> ------------------------------------------------
>
> Key: CB-7606
> URL: https://issues.apache.org/jira/browse/CB-7606
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Affects Versions: 3.5.0
> Reporter: Paul Kane
> Assignee: Shazron Abdullah
> Fix For: 3.8.0
>
>
> I'm not an Obj-C or Cordova programmer so bear with me.
> Let's say my app is running. Then I hop over to my mail app and click on a
> link (myapp://blahBlahBlah) that should open up my app. This works fine, the
> app opens, my own URL handler (in javascript) takes over, etc.
> However in Obj-C the view controller is -- incorrectly, I believe -- storing
> that scheme data (blahBlahBlah) in self.openURL (so that it can be picked up
> later in processOpenURL function, called during webView initialization).
> This isn't normally a problem, except when you move to a new page
> (window.href = "/new_page"), the webView initialization runs again and picks
> up the old (already-acted-upon) openURL variable. (it's then set to nil, so
> that it doesn't get acted upon a third time, fourth time, etc...).
> I might have some details wrong, but it should be fairly easy to walk through
> with a project-wide search for "openurl". Just seems like a slightly wrong
> logic-flow, which unfortunately is interfering with my app.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
