Kyle Seth Gray

Kyle Seth Gray's blog. Usually writing about tech, personal experience, but now leaning more towards health and fitness.

Photoshop on iPad!

That’s it that’s the blog

https://apps.apple.com/us/app/adobe-photoshop/id1457771281

iOS 13 Beta Shenanigans

The tech community exploded last week when Apple released beta 1 of 13.1, before 13.0 was even confirmed GM or hit devices publicly.

There was a lot of speculation and funny bits, people thinking that Apple only develops one piece of software at a time [ha], others saying that 13.0 is somehow so buggy that it's going to be updated right away to 13.1, and the public will never see 13.0, and even more speculation and chaos when a fake document went around trying to spell out the plan.

I think the most obvious thing Apple is doing here is trying to steer clear of what they've done in the past. In past years, iOS beta usually reaches a point during the summer where it needs to work on new hardware. That means prepping it internally for release to devices that are flashed at the factory. In order to support hardware, it's going to have information about that hardware, like, dual-sim support, Face ID, or the brand new iPhone X entirely with its new features and contemporaries in the product line.

So, if you're Apple, what do you do when the late betas are leaking hardware? Or, when employees who have access to the latest seeds hack on top of their boot arguments to get them to display features they aren't supposed to have access to?

You keep the late/final seeds close to heart. So, instead of releasing iOS beta 9, like everyone was expecting, internally and externally, you release the next major release, 13.1. This won't have any of the features that are hidden and exclusive to the near gold master of iOS 13, which is needed on the devices that are shipping next week. But it will have new features that were pushed from the 13.0 release in September, which will allow for more testing, and keep the developer community happy.

Anyways, this whole post is just me speculating off of what little knowledge I have of internal processes. And to be here when 13.0 is actually be released and say "I told you so" to all those people that think that Apple's somehow:

1: Skipping a public release of 13.0
2: Shipping iPhones with 13.1¿¿¿ and not having a great upgrade path
3: Is burning down Apple Park and erupting into chaos because they happened to seed the next Beta before a public release

It would help if Apple Developer Relations, I don't know, had a public post about this? Pushed to say "Maybe don't just auto update people on the latest beta to 13.1?"? Communicated whatsoever? Related to the developers?


Although, I think Apple should've realized that there is a certain developer/user hostile feel to releasing a point update on the same seed as the previous major update, which confuses users who may be public beta testers who may want to revert back to shipping software before November.

Watch Time with Zac Hall

Zac was kind enough to have me on his new Watch Time podcast.

On it, we discussed various parts of my fitness and health journey and how it's affected me personally and professionally. I am really proud of how it turned out, and am super thankful Zac had me on.

Go give it a listen!

https://9to5mac.com/2019/08/14/9to5mac-watch-time-08-14-2019/

Family Sharing - Primary Payment Method

If you're like me, you may be the person in your family that's the expert with technology. And the one setting up devices and services for other family members.

Recently, I finally bumped up against my 200GB iCloud sharing plan. Not wanting to pay for 2TB when I'm barely going to push 200 GB, I looked to join the family sharing account I had set up for my parents and siblings. However, because of how the accounts are set up, I was worried that my app purchasing habits [compared to theirs] would cause issues with the "Primary Payment Method".

If you join as a family member of a Family Sharing account, usually all purchases go through the primary member. This honestly is great for a family with kids, but falls down when there are a bunch of adults taking advantage of shared iCloud Storage or Apple Music.

Thanks to the Apple Support Twitter account, and my habit of buying iTunes gift cards on sales, I found an interesting way to join a family sharing account, but allow say, a particular family member, maintain their different spending habits. Especially if you're like me and tend to buy a lot more apps/music/subscriptions than your family members.

The solution? To allow charges to go directly to your account first, maintain an "Apple ID balance" on your account. By using iTunes gift cards, or just reloading your account through the App Store Account page, you can load money on your personal Apple ID to pay for your subscriptions and purchases. Your Apple ID will always default to this balance before charging the primary family member's account.

I've just started using this, and it'll be interesting to see how receipts work, but I'm glad that I can join a family sharing account, and enjoy the benefits of shared media/purchases, but without having to worry about trying to balance any payments made by the primary account holder.

Adding a Separate Developer Account to your iOS Device

Update: 2/20/19: Apple has updated the Developer Support site with documentation on Two-Factor Authentication.

Apple is now requiring Developer accounts have 2FA turned on as a security measure.

This has led to a lot of confusion because a lot of developers have separate accounts for good reason. Here’s how you can add your developer account to your device to get authentication codes.

  1. Go to Passwords and Accounts on your iOS device.
  2. Add Account
  3. Add iCloud
  4. Sign in to your developer account
  5. Turn off all the switches
  6. Bam
  7. Go to App Store connect or something like that
  8. Try to sign in
  9. You should get two factor codes on that device

  10. [Optional] File a radar to get this process streamlined/clarified.

Despite the account being labeled as ‘inactive’ on that account screen, you have added your device as a “trusted” device capable of receiving two-factor authentication codes.

I did this process after I had activated 2FA on my developer account. But you should be able to sign in this way, then go to appleid.apple.com, and enable Two-Factor Authentication there.

Edit: The one problem is enabling it in the first place - the easiest way is to create a temporary user on your Mac and enable it there, but damn if that isn’t a clunky solution.

Apple Watch - Close Your Rings Stories

in 2017, it was the coolest thing for me to personally be in a testimonial video for the Apple Watch. It showed me how much Apple really cared, in their external and internal messaging, about how the Apple Watch changed people's lives.

It makes me super happy to see even more stories on Apple's Close Your Rings page. All of these videos show unique and interesting people, all striving to do the same thing - close their rings and live a better day.

Check out these stories! They really are neat, especially when it's from every day people like me and you, to professional athletes that enjoy the watch's fitness and connectivity features.

Also, check out Zac Hall's piece on his continuous journey on improving his mental and physical health with the Apple Watch.

Shop on Amazon - Support my random blogs