Bug 12851 - .XIB file will not be compiled into a Xamarin.iOS binding project
Summary: .XIB file will not be compiled into a Xamarin.iOS binding project
Status: CONFIRMED
Alias: None
Product: iOS
Classification: Xamarin
Component: General (show other bugs)
Version: 6.2.x
Hardware: PC Mac OS
: Normal normal
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-06-24 13:33 UTC by Tom Opgenorth
Modified: 2017-10-09 15:22 UTC (History)
6 users (show)

See Also:
Tags:
Is this bug a regression?: No
Last known good build:


Attachments
Error from the (17.01 KB, text/plain)
2013-06-24 13:33 UTC, Tom Opgenorth
Details
Application showing the problem. (375.44 KB, application/zip)
2013-06-24 15:28 UTC, Tom Opgenorth
Details
Test Case (Update for Unified APIs) (410.76 KB, application/zip)
2017-02-28 21:46 UTC, Vincent Dondain [MSFT]
Details

Description Tom Opgenorth 2013-06-24 13:33:25 UTC
Created attachment 4189 [details]
Error from the

Creating a binding project for InfColorPicker (https://github.com/InfinitApps/InfColorPicker).

I've created a static lib for the Objective-C parts and I am trying to create a Xamarin.iOS binding for the project. The .XIB is not compiled into the static library, so I tried to add it to the Xamarin.iOS binding project. This seems to have no effect. iOS cannot load the NIB file. See the attachment error.txt for the exception that is thrown.


The workaround seems to be to add the XIB files to the Xamarin.iOS application project.
Comment 1 Tom Opgenorth 2013-06-24 15:28:21 UTC
Created attachment 4191 [details]
Application showing the problem.

Sample project demoing the problem.
Comment 2 Vincent Dondain [MSFT] 2017-02-28 21:46:02 UTC
I can still reproduce this issue, I updated the test case to unified.
Comment 3 Vincent Dondain [MSFT] 2017-02-28 21:46:49 UTC
Created attachment 20045 [details]
Test Case (Update for Unified APIs)
Comment 4 Alex Soto [MSFT] 2017-04-25 14:56:51 UTC
*** Bug 55522 has been marked as a duplicate of this bug. ***
Comment 5 Alex Soto [MSFT] 2017-04-25 14:59:05 UTC
@Jeff/@Vincent do we have plans to fix this issue?
Comment 6 Alex Soto [MSFT] 2017-04-25 15:00:43 UTC
From #55522

Hello Thanks for contacting us, this is a dupe of bug #12851.

That being said a workaround for this is that you manually compile storyboards to storyboarc and add them to Resources folder in the binding project. using ibtool you can compile them.

ibtool --output-format human-readable-text --compile MyStoryboard.storyboardc MyStoryboard.storyboard
Comment 7 patryk.romanczuk 2017-04-26 11:28:56 UTC
I sucessfully managed to load storyboard in my app from binding library by referencing manually compiled storyboard resource file but it goes with another problem.

Storyboard comes from a Swift Framework (I am aware that it is not officially supported, but it is possible by working with Framework-Swift.h) and referencing such framework in Binding Library results in creating SwiftName attributes in ApiDefinition like this : 

Name = "_TtC15NPUIPlayerTheme24FrameworkViewController"

Obviusly from my code i see this classes as normally named FrameworkViewController, but... when i try to instantiate ViewController from referenced in this way framework it ends with:

Unknown class _TtC15NPUIPlayerTheme24FrameworkViewController in Interface Builder file.

Is there any possible way to workaround this issue? It is crucial for me to use this framework.

Note You need to log in before you can comment on or make changes to this bug.