Re: Triggering a segue from code

2016-09-25 Thread mail...@ericgorr.net
Thank you again for your reply Quincey. 1. I have updated the code to keep a reference to the window controller instead of the window as you suggest. As you suspected, the bad behavior does not change. 2. The reason why I do a performClose is because I want it to do the same thing as when

Detecting user termination of an iOS auto-renewing subscription

2016-09-25 Thread Lou Zell
Hi all, Using the App Store receipt verification system, is there a way to detect when an auto-renewing iOS subscriber terminates their subscription _before_ the expiration date of their current subscription passes? I am referring to a user going through: iTunes > Account > View My Account >

Re: Triggering a segue from code

2016-09-25 Thread mail...@ericgorr.net
Based on stuff I have been playing with, #2 seems like the “right” solution based on the design of the framework. A segue is currently not designed to support this behavior and it is always a mistake, I have learned, to try to fight the framework (which eliminates #1 & #4). > On Sep 25, 2016,

Re: Triggering a segue from code

2016-09-25 Thread Quincey Morris
On Sep 25, 2016, at 11:59 , mail...@ericgorr.net wrote: > > 2. The reason why I do a performClose is because I want it to do the same > thing as when the user presses the close button on the panel, which they are > allowed to do. Unless I were to remove the close button from the inspector >

Re: ITMS-90171 libswiftRemoteMirror.dylib

2016-09-25 Thread Torsten Curdt
Current reading suggests that (whatever ibswiftRemoteMirror.dylib is) this is a difference between xcodebuild archive vs build (for whatever reasons). Since I can't find any further information on this I tried the archive approach: xcodebuild -project "Foo.xcodeproj" -scheme "App"

Subclassing and Archiving/Unarchiving

2016-09-25 Thread Dave
Hi All, I have an App that produces Archives files that are loaded by another App. The Classes that get archived are in a set of common files that both Apps share. During the build process I need to carry extra information that only the writer app knows about. My first instinct was to create

Re: ITMS-90171 libswiftRemoteMirror.dylib

2016-09-25 Thread Torsten Curdt
As for going with "build" instead of "archive" I see this in the log builtin-swiftStdLibTool --copy --verbose --sign 99D83694482D58B0EBB9A85D9528ECC7247A7DB1 --scan-executable /project/build/iphoneos10.0/Applications/Foo.app/Foo --scan-folder

Re: ITMS-90171 libswiftRemoteMirror.dylib

2016-09-25 Thread Torsten Curdt
As it turns out xcodebuild logs the actual error somewhere before and just gives the summary at the end. The error building the archive was a library that didn't have bitcode enabled. Oh well. Still would love to understand why "build" adds the " libswiftRemoteMirror.dylib" though. On Sun, Sep

Re: Subclassing and Archiving/Unarchiving

2016-09-25 Thread Graham Cox
> On 25 Sep 2016, at 8:12 PM, Dave wrote: > > Is there any way that I can get the archiver to just select the Base Class > and ignore the extra properties in the Subclass? Or is there a better way of > doing this? You mean the dearchiver. It can have a delegate