4 ms·

Wasted 3h when this didn't work with my iPhone 12 pro, but did work with my wifes 11 pro. Was so confused...

• drmpeg 5y ago
  It seems like Apple actively tries to ruin the functionality of libimobiledevice with each release of iOS. It worked the best on my iPhone 6 and iOS 9.3.4.
  • amelius 5y ago
    When do people realize that an iPhone is not a general purpose computer and was never intended to be one?
    • nabla9 5y ago
      Computer appliance, a computing device with a specific function and limited configuration ability.
    • kmeisthax 5y ago
      When Apple marketing stops saying otherwise.
    • machello13 5y ago
      Have you considered that your idea of a general purpose computer might just be different than pretty much everyone else?
    • CameronNemo 5y ago
      I think iphone owners on here understand what apple intends for their devices, but simply like the alternatives less. So they try and hack around the restrictions placed on their iphones.
    • smoldesu 5y ago
      Because the iPhone is capable of being a general purpose computer, and the only one stopping it from being one so far is Apple.
      • bitwize 5y ago
        General purpose computers, as we understand them, are a niche market and potentially quite harmful in untrained hands. Apple is targeting the mainstream consumer. They still sell GPCs though, under the Mac brand.
        • smoldesu 5y ago
          Apple is welcome to build the "mainstream computer", but they should do so with respect to the protocols and open-source space around them. If they continue their oppressive approach to hardware and software development, they'll have a hard time defending themselves when people accuse them of a monopoly.
        • joshspankit 5y ago
          Even more harmful: smaller and smaller numbers of people who actually understand how computers work.
  • filleduchaos 5y ago
    It seems even stranger to me to consider it an active effort. More likely to me that engineering teams at Apple simply don't give much of a shit about maintaining compatibility with a tool that's not affiliated with them, and will redesign things or make breaking changes as it suits their project goals - and unaffiliated tools like this are simply stuck in a perpetual game of catchup.
    • smoldesu 5y ago
      > and unaffiliated tools like this are simply stuck in a perpetual game of catchup. So it's still a problem. Apple knows about these unaffiliated tools, and they do very little to maintain communique with them until it's convenient for Apple to do so. This is nothing new, and it's one of the reasons you couldn't pay me to develop on iOS these days.
      • filleduchaos 5y ago
        But why should they maintain communications with them? Don't get me wrong, it would certainly be nice of them to, but I don't see how someone else doing unaffiliated, unrequested, unguaranteed work based on my own work creates any sort of obligation for either of us.
        • smoldesu 5y ago
          I figure that it would be a good way for the world's most valuable company to give back to their core userbase, and it would certainly be a step in the right direction for helping developers like me who are highly skeptical of Apple's commitment to building a robust developer ecosystem. They need all the help they can get, because it's starting to look less and less viable for me to switch to a Mac as time goes on. It will be interesting to watch how they reconcile pressure from developers over the next few years.
• swills 5y ago
  Strange, it's working fine for me on iOS 15 beta, but I'm using an older iPhone XS. I would expect the OS version to matter more than the hardware.
• voltagex_ 5y ago
  Worked with my 12 Pro a few weeks ago - did you try the latest version from Git?
  • amluto 5y ago
    Some distros package outdated versions. The git version seems to work fine.