Just put the files anywhere I guess.
𓃗
art blog(derogatory)
Aqua Utopia|海の底で記憶を紡ぐ
we're not kids anymore.
No title available

Discoholic 🪩

No title available

if i look back, i am lost
almost home
Not today Justin
The Stonewall Inn
Cosmic Funnies

bliss lane
YOU ARE THE REASON
$LAYYYTER
No title available
wallacepolsom
let's talk about Bridgerton tea, my ask is open

#extradirty
Monterey Bay Aquarium
seen from United States
seen from United States
seen from Russia

seen from Canada

seen from Türkiye
seen from United States

seen from France
seen from United States
seen from Malaysia
seen from Azerbaijan

seen from United States
seen from United States

seen from Netherlands

seen from Malaysia
seen from T1
seen from United States
seen from Venezuela

seen from T1

seen from Canada

seen from United States
@textfromxcode
Just put the files anywhere I guess.
I assume this is a security measure.
I updated to Swift 3 again. Maybe it’ll take this time.
Followup to the last post: Some days you just can’t click a button.
I should be developing on a device anyway, right?
Sometimes Xcode just needs to rest for a moment.
Xcode probably supports some versions of iOS, but nobody's sure which ones.
I was going to file a Radar about this, but Radar’s web interface is down. I’m not even kidding.
If you're editing a file, that means a file with that file's name exists. Who knew?
Who are you going to trust, Xcode or some freaky open source project?
Xcode vs. iTunes, the battle continues.
No, Xcode, for real, WTF does that actually mean?
Xcode has to SEE you unlock a phone. It’s not just gonna believe you.
Vague warning messages help keep developer minds sharp by forcing them to work out where the problem is.
I think Xcode is just straight out trolling me now.
Schrödinger’s Playground
True fact: For Xcode, time flows in reverse.
Please jump through some hoops. No, it won’t help anything.
Someone, please tell Xcode about Swift? Thanks.