home.social

#appledevelopment — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #appledevelopment, aggregated by home.social.

  1. Swift 6.3.2 is here - a maintenance release with critical bug fixes and stability improvements after the major 6.3 release. Recommended for all developers.

    🔗: forums.swift.org/t/announcing- by Mishal Shah (@shahmishal)

    #Swift #iOSDev #AppleDevelopment

  2. Swift 6.3.2 is here - a maintenance release with critical bug fixes and stability improvements after the major 6.3 release. Recommended for all developers.

    🔗: forums.swift.org/t/announcing- by Mishal Shah (@shahmishal)

    #Swift #iOSDev #AppleDevelopment

  3. Swift 6.3.2 is here - a maintenance release with critical bug fixes and stability improvements after the major 6.3 release. Recommended for all developers.

    🔗: forums.swift.org/t/announcing- by Mishal Shah (@shahmishal)

    #Swift #iOSDev #AppleDevelopment

  4. Swift 6.3.2 is here - a maintenance release with critical bug fixes and stability improvements after the major 6.3 release. Recommended for all developers.

    🔗: forums.swift.org/t/announcing- by Mishal Shah (@shahmishal)

    #Swift #iOSDev #AppleDevelopment

  5. I get why it needs to happen, but needing an App Store Review to push a build to external testers pisses me off so much.

    I kinda wish Apple would just drop the ban hammer on people abusing external testing instead, but I've read enough reports of people being banned "for no reason" I'm not sure I trust that, either. Even if most of them are probably lying. #AppleDevelopment

  6. I get why it needs to happen, but needing an App Store Review to push a build to external testers pisses me off so much.

    I kinda wish Apple would just drop the ban hammer on people abusing external testing instead, but I've read enough reports of people being banned "for no reason" I'm not sure I trust that, either. Even if most of them are probably lying. #AppleDevelopment

  7. I get why it needs to happen, but needing an App Store Review to push a build to external testers pisses me off so much.

    I kinda wish Apple would just drop the ban hammer on people abusing external testing instead, but I've read enough reports of people being banned "for no reason" I'm not sure I trust that, either. Even if most of them are probably lying. #AppleDevelopment

  8. I get why it needs to happen, but needing an App Store Review to push a build to external testers pisses me off so much.

    I kinda wish Apple would just drop the ban hammer on people abusing external testing instead, but I've read enough reports of people being banned "for no reason" I'm not sure I trust that, either. Even if most of them are probably lying. #AppleDevelopment

  9. I get why it needs to happen, but needing an App Store Review to push a build to external testers pisses me off so much.

    I kinda wish Apple would just drop the ban hammer on people abusing external testing instead, but I've read enough reports of people being banned "for no reason" I'm not sure I trust that, either. Even if most of them are probably lying. #AppleDevelopment

  10. Apple, you want to use AI somewhere actually useful?

    How about I type in a Description of a bug in Feedback Assistant, hit something, and it guesses which area I'm seeing the issue in?

    That popup list is long enough to be useless, and it never has anything relevant.

    From now on I'm just picking "Something else on this list" without looking. #appleDevelopment

  11. Apple, you want to use AI somewhere actually useful?

    How about I type in a Description of a bug in Feedback Assistant, hit something, and it guesses which area I'm seeing the issue in?

    That popup list is long enough to be useless, and it never has anything relevant.

    From now on I'm just picking "Something else on this list" without looking. #appleDevelopment

  12. Apple, you want to use AI somewhere actually useful?

    How about I type in a Description of a bug in Feedback Assistant, hit something, and it guesses which area I'm seeing the issue in?

    That popup list is long enough to be useless, and it never has anything relevant.

    From now on I'm just picking "Something else on this list" without looking. #appleDevelopment

  13. Apple, you want to use AI somewhere actually useful?

    How about I type in a Description of a bug in Feedback Assistant, hit something, and it guesses which area I'm seeing the issue in?

    That popup list is long enough to be useless, and it never has anything relevant.

    From now on I'm just picking "Something else on this list" without looking. #appleDevelopment

  14. Apple, you want to use AI somewhere actually useful?

    How about I type in a Description of a bug in Feedback Assistant, hit something, and it guesses which area I'm seeing the issue in?

    That popup list is long enough to be useless, and it never has anything relevant.

    From now on I'm just picking "Something else on this list" without looking. #appleDevelopment

  15. Apple just approved my new app first try, and in less than 24 hours.

    I… I… I don’t know what to do with this. What the actual fuck? What do I do now?!? #appleDevelopment #iosDevelopment

  16. Apple just approved my new app first try, and in less than 24 hours.

    I… I… I don’t know what to do with this. What the actual fuck? What do I do now?!? #appleDevelopment #iosDevelopment

  17. Apple just approved my new app first try, and in less than 24 hours.

    I… I… I don’t know what to do with this. What the actual fuck? What do I do now?!? #appleDevelopment #iosDevelopment

  18. Apple just approved my new app first try, and in less than 24 hours.

    I… I… I don’t know what to do with this. What the actual fuck? What do I do now?!? #appleDevelopment #iosDevelopment

  19. Apple just approved my new app first try, and in less than 24 hours.

    I… I… I don’t know what to do with this. What the actual fuck? What do I do now?!? #appleDevelopment #iosDevelopment

  20. Xcode 26.4's Release Notes subheadings include anchors, but unfortunately the anchor IDs are the text of the subheading.

    There are a lot of #Resolved-Issues anchors in that document. #AppleDevelopment

  21. Xcode 26.4's Release Notes subheadings include anchors, but unfortunately the anchor IDs are the text of the subheading.

    There are a lot of #Resolved-Issues anchors in that document. #AppleDevelopment

  22. Xcode 26.4's Release Notes subheadings include anchors, but unfortunately the anchor IDs are the text of the subheading.

    There are a lot of #Resolved-Issues anchors in that document. #AppleDevelopment

  23. Xcode 26.4's Release Notes subheadings include anchors, but unfortunately the anchor IDs are the text of the subheading.

    There are a lot of #Resolved-Issues anchors in that document. #AppleDevelopment

  24. Xcode 26.4's Release Notes subheadings include anchors, but unfortunately the anchor IDs are the text of the subheading.

    There are a lot of #Resolved-Issues anchors in that document. #AppleDevelopment

  25. Simplifying, but Apple offered APIs using two path kinds: HFS uses colon as a path separator, POSIX uses slash. 25 years later, the HFS APIs are mostly dead. We just use POSIX.

    I just wrote a file with a colon in the name and sent it to the iOS share sheet… which shows a slash.

    I was going to convert both to hyphen/minus (the low ASCII one) out of paranoia anyway, plus 2026:03:25 is weird. I just wanted to see what would happen: I write POSIX, it shows HFS. Avoid both! #AppleDevelopment

  26. Simplifying, but Apple offered APIs using two path kinds: HFS uses colon as a path separator, POSIX uses slash. 25 years later, the HFS APIs are mostly dead. We just use POSIX.

    I just wrote a file with a colon in the name and sent it to the iOS share sheet… which shows a slash.

    I was going to convert both to hyphen/minus (the low ASCII one) out of paranoia anyway, plus 2026:03:25 is weird. I just wanted to see what would happen: I write POSIX, it shows HFS. Avoid both! #AppleDevelopment

  27. Simplifying, but Apple offered APIs using two path kinds: HFS uses colon as a path separator, POSIX uses slash. 25 years later, the HFS APIs are mostly dead. We just use POSIX.

    I just wrote a file with a colon in the name and sent it to the iOS share sheet… which shows a slash.

    I was going to convert both to hyphen/minus (the low ASCII one) out of paranoia anyway, plus 2026:03:25 is weird. I just wanted to see what would happen: I write POSIX, it shows HFS. Avoid both! #AppleDevelopment

  28. Simplifying, but Apple offered APIs using two path kinds: HFS uses colon as a path separator, POSIX uses slash. 25 years later, the HFS APIs are mostly dead. We just use POSIX.

    I just wrote a file with a colon in the name and sent it to the iOS share sheet… which shows a slash.

    I was going to convert both to hyphen/minus (the low ASCII one) out of paranoia anyway, plus 2026:03:25 is weird. I just wanted to see what would happen: I write POSIX, it shows HFS. Avoid both! #AppleDevelopment

  29. Simplifying, but Apple offered APIs using two path kinds: HFS uses colon as a path separator, POSIX uses slash. 25 years later, the HFS APIs are mostly dead. We just use POSIX.

    I just wrote a file with a colon in the name and sent it to the iOS share sheet… which shows a slash.

    I was going to convert both to hyphen/minus (the low ASCII one) out of paranoia anyway, plus 2026:03:25 is weird. I just wanted to see what would happen: I write POSIX, it shows HFS. Avoid both! #AppleDevelopment

  30. This has been a frequent friend in Xcode 26.3. Line 22 is only about 22 characters, so I don't know what it's on about. #xcode #AppleDevelopment