Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invite controller also broken for iPad #50

Open
francisjervis opened this issue Jul 27, 2016 · 4 comments
Open

Invite controller also broken for iPad #50

francisjervis opened this issue Jul 27, 2016 · 4 comments

Comments

@francisjervis
Copy link
Contributor

Just saw this one:

Fatal Exception: NSInternalInconsistencyException
Could not load NIB in bundle: 'NSBundle </var/containers/Bundle/Application/32579E05-90AB-4C3F-9D9E-E86FE2FFCB04/TimesFree.app/BranchInvite.bundle> (not yet loaded)' with name 'BranchInviteViewController'

@aaustin
Copy link
Contributor

aaustin commented Jul 31, 2016

I just added xibs for ipad specifically in this commit and updated cocoapods. I couldn't get it to crash on an iPad, but can you give the latest a try? 0324253

@francisjervis
Copy link
Contributor Author

francisjervis commented Aug 3, 2016

Looking good! Found one issue: the controller dismisses when the "done" button is tapped with the "Text" tab selected (ie sending iMessage/SMS). The app does not crash, though. This does not happen on small screens. Email functionality works works fine on all devices.

Should this release fix #49?

@aaustin
Copy link
Contributor

aaustin commented Aug 3, 2016

So, it doesn't actually send SMS even when contacts are selected? Hmm and this only happens on iPad?

Somehow I missed the #49 issue. Did you test it and it worked?

@francisjervis
Copy link
Contributor Author

Ha I found what it was - the iPad in question didn't have iMessage activated!! This causes the invite controller to dismiss silently.

Ideally I'd like to handle this differently from user-initiated cancels (ie the invitesCanceled delegate method). Arguably the SDK should alert the user in the case of failure as it does when loadContactsFromAddressBookIfPossible fails. Low priority tho!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants