It worked!!!
Hooray! So just as you suggested, when I built in Xcode, ONLY the platform specific sprites showed up
.
Loads fine now on the 4s!
So the question is-- what the heck was I doing wrong before??
I think there are four possibilities?
1) There is a *chance* that maybe I only tested 4s with 2x. I can't imagine why I would only do that-- but my memory's a little fuzzy on it now. But 2x makes it crash. Only going down to 1x gets it to run. So if I initially was stupid and didn't check 1x that would explain the crash. I think I did check 1x though??? I can't remember.
2) In my successful test, I built 1x and it worked on 4s. I then switched to 2x and it crashed. I switched back to 1x and it crashed again! I then went into tk2d preferences and changed the default editor platform to 1x. This time at 1x it worked again. Tried again to make sure and it's running fine. I'm not sure if changing the default platform to 1x actually helped-- in my experience the 4s has so little ram that sometimes it just chokes randomly if you've pushed the device too much without a restart. So maybe switching tk2d preferences to default 1x had an effect-- though I suspect maybe the phone just glitched out.
3) The only other real thing I did is when you asked me to print the textures showing up, I noticed all the platform specific atlases were defaulting to the same name: atlas0. 1x, 2x and 4x sprites were all called atlas0. So I manually changed the names of those atlases so I could see what was happening in debug. (i.e. I changed to myatlas01_1x, myatlas01_2x, myatlas01_4x). I have no idea whether that had an impact or not. Could tk2d have confused the atlases if they were all called atlas0?? I doubt it cuz it looks like it's all folder based. But anyway, that's something I did and now it's working.
4) Most likely-- I did something stupid and I'm not sure what. lol I am prone to doing dumb stuff-- so maybe there was some script of mine that I screwed up on and subsequently got rid of between crash and success? I am certain that the 4s was originally crashing due to memory pressure. that was the Xcode error. Anyhow, it is definitely possible that some dumb script of mine was responsible for the error.
Anyway, it's all working now! Sucks that I'm still a little fuzzy as to why it's working now and wasn't before? But mainly I'm grateful to have it running!!
Thank you so much, Unikron for your awesome software and support!! I'm heading over to the asset store now to amend my already very positive review to make it more positive.
Thanks again. I'm super grateful for all of your help.
Sebastian
(funAsylum on asset store)