Bad news, this regressed today. Got a build rejected again withNon-public API usage:The app references non-public symbols in Frameworks/libswiftNetwork.dylib: _NWCreateDispatchDataFromNSData, _NWCreateNSDataFromDispatchData, _nw_endpoint_copy_interface, _nw_endpoint_create_unix, _nw_endpoint_set_interface, _nw_interface_create_with_index, _nw_interface_create_with_name, _nwlog_get_string_for_dns_service_error
My thanks to both of you -- super awesome not to have to pull this lever without knowing if it means my app cannot be purchased anymore or not 🙂
UPDATE: I talked with Apple today, and uploaded 2 builds of 2 apps successfully -- as of Friday Sept. 28 this is fixed.
Post not yet marked as solved
Hi bford,There were always people in the frame.The portrait matte is simply not generated in potrait orientation even if there are people present, and the exact same people present in landscape orientation makes it work.One thing I had an idea about: I had hard-set the AVCaptureConnection.videoOrientation to .landscapeRight. Perhaps the portraitMatte generation requires the image to be in .up configuration to find the faces etc? To test this i've started to set .videoOrientation as the device rotates.I don't have the device anymore to try this out, but I will soon.
Thanks Quinn - really appreciate your help as always!It is a bit painful delaying the beta & the release of our apps for iOS 12 because of this bug (we bet on Network.framework), hope they can sort it out soon
Borrowed an iPhone 8 Plus.Yes, portraitEffectsMatte can indeed handle more than one person in a frame! I tried with up to 4 people, at various depths (together, apart, some/none/lots of lateral distance), and it worked much better than I expected (almost always "caught" all 4 people in the matte).GREAT job Apple.
Thanks, I filed bug 44603506. I filed under "App Store" which is probably incorrect
Post not yet marked as solved
Thanks for the quick response.To get this far, the user must have gotten to authorizationStatus == .authorized.But one thing that occurred to me since my last post: on slower devices, it could be that these lines of code are running multiple times concurrently (on multiple threads). In that case, each instance will call its own performChanges()Is that supported?... also please keep in mind, I cannot reproduce this myself. So although I have full thread stacktraces from Fabric/etc, I don't have anything more
Oops, it was 54m:10-15s, and it's the Portrait Segmentation API. It is erroneously referred to in the WWDC 2018 State of the Union video by the presenter as the "People Segmentation API".
Update: it worked, thanks. This new IAP is live on the app store.
Post not yet marked as solved
Hi Eskimo,I can't move to peer-to-peer wifi, because as I alluded to in my original post (but only in parentheses, sorry), the wifi of the iPad/iPhone is directly connected to a DSLR camera's wifi. That is, it has a 1-1 wifi connection to a Canon/Nikon/etc camera. I did explore Multipeer-like solutions which appear to still facilitate connectivity of other iOS devices while connected to camera, I presume by somehow multiplexing the wifi connectivity. The issue is that the throughput to the camera (vital for live-view) drops to approx 100kB/sec, compared to 1mB/sec which is normal.So for this photobooth app, peer-to-peer Bluetooth is absolutely critical/vital, and I have to rely on dns_sd.h as far as I can see.(that framework of mine that I linked to, BluePeer, does also support peer-to-peer wifi; the photobooth app i'm referring to only uses bluetooth for it)For future apps I write, I certainly won't use dns_sd.h unless they have equally (strict) restrictions ...Makes sense?
Post not yet marked as solved
Update: on the stackoverflow post (link in original post), people are saying that this is new in beta 5 (ie. beta 4 works for them)
Post not yet marked as solved
Thanks Quinn for the response.I filed "bug" 41099437 for Network.framework (possibly in the wrong place)Re no longer supporting peer-to-peer networking over Bluetooth in iOS 11, hmm. I am using my own stack that I built ... https://github.com/xaphod/Bluepeer... which provides headless P2P over Bluetooth and/or wifi. It uses dns_sd.h via HHServices, which handily does support building P2P Bluetooth networks for me via Bonjour in iOS 11.Are you saying that this is a fluke, and might stop working any time? Or is the deprecated stuff only via NSNetService (which I am not using) ?It would be a real shame if this suddenly stopped working in iOS 12, because it is a simply KILLER feature: event guests walk up to the photographer's iPad with the app installed, without being on any wifi network, and the app on their iPhone auto-discovers the iPad and allows the guest to take photos via the photographer's iPad (which is likely driving the photographer's big expensive DSLR via ipad's wifi).My users love this functionality: they walk up to the iPad, take photos with the photographer's pro setup, and instantly have the photos on their iPhones...
Awesome. Can you verify that you have at least one app that does this, approved on the app store? thanks!
Post not yet marked as solved
I get this when I attempt to CGContextDrawImage a CGImage that's backing a UIImage.I've hit this in the debugger a few times now.When I attempt to display the UIImage in the debugger, I see the following additional lines then added to the console:2018-02-23 18:19:00.963013-0500 Photobooth[1455:1000835] handle_error:351: zlib error2018-02-23 18:19:00.963113-0500 Photobooth[1455:1000835] handle_error:351: No IDATs written into file(lldb)
