Bug 25910 - OpenUrl is not called
Summary: OpenUrl is not called
Status: RESOLVED NORESPONSE
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.3.0
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-01-11 15:51 UTC by uwantfries
Modified: 2016-04-13 17:55 UTC (History)
6 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description uwantfries 2015-01-11 15:51:26 UTC
Repro: 
Create a new Forms shared project.
Add custom url to info.plist
override OpenUrl with :

public override bool OpenUrl (UIApplication application, NSUrl url,
			string sourceApplication, NSObject annotation)
		{
			System.Diagnostics.Debug.WriteLine (">>>>>>>>>>>>>>>> OpenUrl");
			Console.WriteLine (url.ToString());
			/* now store the url somewhere in the app’s context. The url is in the url NSUrl object. The data is in url.Host if the link as a scheme as superduperapp://something_interesting */
			return true;
		}

launch app from custom url link.
App lauches sucessfully but OpenUrl is not called and 

Jan 11 20:42:56 Vikkis-iPod-touch TestUrlSchemeiOS[1727] <Warning>: MonoTouch: Could not bind to address: Address already in use
Jan 11 20:42:56 Vikkis-iPod-touch TestUrlSchemeiOS[1727] <Error>: assertion failed: 12B411: libxpc.dylib + 51955 [04694BEB-256F-3132-A00F-0C82B79BC689]: 0x7d
Jan 11 20:42:56 Vikkis-iPod-touch Unknown[1727] <Error>:

is seen in the event log.


System version attached:

Xamarin Studio
Version 5.5.4 (build 15)
Installation UUID: 8e6fa004-2eac-43d7-adae-86b4c4b6667c
Runtime:
	Mono 3.10.0 ((detached/92c4884)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 310000031

Xamarin.Android
Version: 4.20.0.28 (Indie Edition)
Android SDK: /Users/vikkikeane/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.1   (API level 7)
		2.2   (API level 8)
		2.3   (API level 10)
		3.1   (API level 12)
		4.0.3 (API level 15)
		4.4   (API level 19)
		5.0   (API level 21)
Java SDK: /usr
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)

Apple Developer Tools
Xcode 6.1.1 (6611)
Build 6A2008a

Xamarin.Mac
Version:

Xamarin.iOS
Version: 8.4.0.47 (Indie Edition)
Hash: 7244769
Branch: 
Build date: 2014-12-11 14:54:30-0500

Build Information
Release ID: 505040015
Git revision: f93940a35458a18052f1a25e106e62ca970d9c40
Build date: 2014-11-19 15:32:41-05
Xamarin addins: dc23cbd91a3a0e1d326328e1229e86c942a49ec8

Operating System
Mac OS X 10.9.5
Darwin Vikkis-Mac-mini.local 13.4.0 Darwin Kernel Version 13.4.0
    Sun Aug 17 19:50:11 PDT 2014
    root:xnu-2422.115.4~1/RELEASE_X86_64 x86_64
Comment 1 uwantfries 2015-01-11 15:57:44 UTC
Looks like its a forms problem. Clean raw iOS only project works fine.
Comment 2 Udham Singh 2015-01-12 12:11:20 UTC
We have tried to reproduce this issue but not able to reproduce this.

Could you please provide a sample app that demonstrate this issue? So that we can reproduce this issue at our end.

Thanks!
Comment 3 Samantha Houts [MSFT] 2016-04-13 17:55:54 UTC
Thank you for your bug report. As we have not received the information requested, we cannot properly triage your bug and are marking it resolved.

Warm regards,
Xamarin Forms Team