Educate me. Why?Well, once it was Apple, good that they ditched the “just works” slogan long time ago, at least they saw it coming.
Just like they recently ditched the iPhone and privacy campaigns, I’m sure you now know why!
Educate me. Why?Well, once it was Apple, good that they ditched the “just works” slogan long time ago, at least they saw it coming.
Just like they recently ditched the iPhone and privacy campaigns, I’m sure you now know why!
The current firmware version on these is 1.0.5, and that's not a new update. The adapter works fine with my iPhone 8 and 13 Pro running 16.5 but doesn't work with iPads running 16.5.Edit:
I attached also FW info from Settings-General-About-Apple USB Camera Adapter page. My FW before update is 1.0.1
Here are screenshots:
Apple has a pretty damn good QA department and the amount of things they check before public release would blow your mind.Does Apple have a QA department??? Like seriously. This is a BASIC part of a release test pass.
Pretty damn good = based on what?Apple has a pretty damn good QA department and the amount of things they check before public release would blow your mind.
Apple's QA dept has been MIA for years! No revenue stream there.Apple has a pretty damn good QA department and the amount of things they check before public release would blow your mind.
This, 100%. Just looking at the code changes is only going to catch any immediate bugs in that piece of code - those are also the ones that are simple to fix. The bigger problems usually only show up in workflows that are often times impossible to create in a testing scenario, especially given the time usually given to test changes. Every user has their own way of doing things that often uncover issues that would be very difficult for someone to encounter when doing software testing.Code paths are unpredictable based on base hardware, external hardware, network, etc. You can't find all bugs by just looking at the code, particularly when you have a code base that is likely millions of lines and may dependent on modules written by another group. Often bugs need reproducible test cases to point a developer in the right direction. The really hard bugs are those which are intermittent and not easily reproducible.
As an example I have a case now in development where a folder in iCloud can't be moved to an external drive. Had to provide tons of diagnostic reports to help them determine where in the code it is failing. You can catch some bugs by just looking at code if you are lucky but that is definitely not always the case.
Another example. Had an issue with an anti-virus program frequently mentioned on this site. It took us maybe 3 months going back and forth to get them enough information so they could identify where the problem was in their code. Took another maybe 6 months for the fix to show up in an actual release since it evidently required a substantial code rewrite.
The reversal conclusion is, that Apple Developers are so bad at coding that even their QA department can’t handle it, because Apples codebase is like a minefield.Apple has a pretty damn good QA department and the amount of things they check before public release would blow your mind.
I guess the fixes for three zero-day bugs in webkit were more important to them, so they shipped. I can understand that.Pretty damn good = based on what?
The bug got reported but they shipped it anyways. Like so many times before, they simply don't care.
Needs MR coverage for them to act.
I use CCK3 with my iPhone.I’m guessing nobody in the iOS 16.5 customer or developer beta had this dongle since the point of the beta is to catch these bugs before they get released to the general public.
Yep. Especially the Homekit Team.Apple has a pretty damn good QA department and the amount of things they check before public release would blow your mind.
I guess the fixes for three zero-day bugs in webkit were more important to them, so they shipped. I can understand that.
I tested my Lightning to USB-3 adapter, it will not work with a 40W USB-C power supply from Anker, as well as with an older Anker powerbank with USB-A. If I connect the Lightning to USB-3 adapter with a USB-C to Lightning cable to the 20W Apple USB-C power supply or to a fairly new powerbank with USB-C connection, it does works.
Apple's Lightning to USB 3 Camera Adapter does not work with iPhones and iPads that have been updated to iOS 16.5 and iPadOS 16.5, according to several users across the MacRumors Forums, Apple Support Community, and Reddit.
![]()
The adapter has a USB-A port for connecting a camera, microphone, or other USB-powered accessory to an iPhone or iPad, along with a Lightning port for charging the iPhone or iPad. As of iOS 16.5 and iPadOS 16.5, however, affected users say the adapter no longer powers any devices connected to both of the ports.
The issue is likely due to a software bug that will need to be addressed in a future iOS version, but the underlying cause is unknown. Apple seeded the first beta of iOS 16.6 to developers today, but the update is likely many weeks away from being released, so an iOS 16.5.1 update might be necessary if the company wishes to fix the bug sooner.
Apple released iOS 16.5 on Thursday following seven weeks of beta testing. The update is a relatively minor one, with additions including a Sports tab in the Apple News app, a new Pride Celebration wallpaper honoring the LGBTQ+ community and culture, and bug fixes related to CarPlay, Screen Time, and Spotlight. Apple is expected to announce iOS 17 with bigger changes during its WWDC keynote on June 5.
Article Link: Apple's Lightning to USB 3 Camera Adapter Not Working With iOS 16.5
Just as Logic Pro is being released, apple is telling owners of eight and ninth gen iPad owners to get f*cked ?
Apple's Lightning to USB 3 Camera Adapter does not work with iPhones and iPads that have been updated to iOS 16.5 and iPadOS 16.5, according to several users across the MacRumors Forums, Apple Support Community, and Reddit.
![]()
The adapter has a USB-A port for connecting a camera, microphone, or other USB-powered accessory to an iPhone or iPad, along with a Lightning port for charging the iPhone or iPad. As of iOS 16.5 and iPadOS 16.5, however, affected users say the adapter no longer powers any devices connected to both of the ports.
The issue is likely due to a software bug that will need to be addressed in a future iOS version, but the underlying cause is unknown. Apple seeded the first beta of iOS 16.6 to developers today, but the update is likely many weeks away from being released, so an iOS 16.5.1 update might be necessary if the company wishes to fix the bug sooner.
Apple released iOS 16.5 on Thursday following seven weeks of beta testing. The update is a relatively minor one, with additions including a Sports tab in the Apple News app, a new Pride Celebration wallpaper honoring the LGBTQ+ community and culture, and bug fixes related to CarPlay, Screen Time, and Spotlight. Apple is expected to announce iOS 17 with bigger changes during its WWDC keynote on June 5.
Article Link: Apple's Lightning to USB 3 Camera Adapter Not Working With iOS 16.5
Great input. Maybe its a case of what poweradapter is being used then?The Apple USB-A Ethernet adapter works here, with the official Apple 20W USB-C charger (A2347) and an official Apple USB-C to Lightning cable. I tried both my iPhone 13 and iPad 10.5. I can also attach a Samsung T5 SSD and several USB-sticks, so the devices are powered.
iPad:
View attachment 2206303
View attachment 2206306
iPhone:
View attachment 2206305
Yes, I guess so. The 20W powerplug is a MFi-certified USB-C charger. I also have an Anker PowerPort Atom III Slim USB-C GaN charger this also works with the Lightning to USB 3 Camera Adapter.Great input. Maybe its a case of what poweradapter is being used then?