I finally got some time to play around with this. My ultimate goal is to let users of 360 cameras pull files via a wire, which has to be a lot faster than using HTTP.
In any case, I have a few 360 cameras with micro-USB connectors. I can plug them into my Mac, and because the camera exposes its storage as a MS-FAT storage device, the Mac can examine the directories and see all the files.
I have a known good Lightning <-> USB-Micro cable (Insta brand, have used it to wire the Insta camera to my App as an External Accessory). When I plug the camera into the Mac, it flashes a blue LED to indicate a connection. When I plug the same camera into my iPhone, running the test app I wrote, it never appears in the Browser "Locations" list. I tried multiple cameras, restarting my app after the connection, etc. Never changes.
I'm now fearing that iOS cannot mount a FAT formatted storage device. Is all hope lost?
CODE:
let documentPicker = UIDocumentPickerViewController(forOpeningContentTypes: [UTType.directory, UTType.mpeg4Movie], asCopy: true) // ios14
documentPicker.delegate = self
documentPicker.allowsMultipleSelection = false
documentPicker.modalPresentationStyle = .fullScreen
present(documentPicker, animated: true, completion: nil)
Post
Replies
Boosts
Views
Activity
Your link to the adapter was the golden key! Now everything works fine for most of my cameras - I get same results using Files as with my own app. Thank you ever so much (I totally did not know about this adapter!)
One wrinkle - it seem that one camera does not appear as a FAT storage device, but instead offers a PTP protocol interface that both "Image Capture" and Photos can use on the Mac, and also Photos on iOS.
But - is there anyway using any iOS device (like one with a USB-C) or any adapter/cable - so my app could also use PTP to retrieve files? [Previous unanswered question in this but its years old: On iPad Pro, is there any way to access USB device by PTP/MPT with USB-C “wired” connection?
I thoroughly searched the project and can find no protocol extension to handle this. All I can conclude at this time is that the original developers, years ago, discovered themselves that they could not get rtsp to work, but then just left the code they had written in the app. Its just so bizarre!
Thanks so much for your response!
I'm on latest iOS 15.5. Building on latest Xcode. Trying to test out some other code in a really large mostly Objective-C app. An no, I don't get a crash just the message. Obviously something is generating it.
Why would me making ranges have anything todo with it? I'm bottlenecking it at the bottom of the app.
The string length varies from run to run. Even it if was always 43, then what would I do? Bottle neck as I have and test for string length == 43? I'm already testing location.
iOS 15 having to put this view as subview 1 - 0 doesn't work for the date view.
Thanks! It occurred to me after posting this might be the case. But why Apple is the default in ios16 different than the past? Lots of ****** off customers…