Wrong custom launch image and Crash in iOS 13.1.3
Binny
Seoul, KoreaMember, PRO Posts: 75
The update build (ver1.1.8) was rejected by Apple because of a problem.
in iOS 13.1.3
- Wrong custom loading image
- Crash in pause (not Pause Game Attribute, make custom pause game)
I tested again with the latest build (ver1.1.8) in test flight.
1) No problem with iOS 12.2(iPhone)
2) The above problem occurs in iOS 13.1.3(iPad)
Test with old build (ver1.1.5: build 2 weeks ago)
1) No problem in iOS 13.1.3(iPad)
In case of Crash, I thought there might be a mistake while updating,
so I'm going to build and test it again without touching the old build.
**in My macOS Mojave 10.14.4 Xcode 10.2.1
Thank you.
Comments
You might be best off using a splash screen with no image for now - for example all black or all white.
@MusicBoutique Yes, that's one of the ways. Thank you.
I tested again a build published without touching the old build(ver1.1.5).
It also has a problem in ios 13.
I think it might be the relationship between the recently changed RC and ios 13.
or Build in mac os Mojave 10.14.4 Xcode 10.2.1 is uncompatibility with ios13?
So I moved the old RC to mainline to get it out of the way for the new RC. I'll look into this, I have a feeling it's from some changes to the loading image stuff that I might have flubbed in the plist.
Not sure about the crash on pause, so thanks for reporting that.
@adent42 Thank you for reply.
For Crash, I'm checking again what's happening when it's paused.
And I'm looking at the crashlog I received from Apple, but I'm not sure.
I'm studying how to view log files.
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 CubeLand 0x0000000105247f44 0x104fbc000 + 2670404
1 CubeLand 0x0000000105249ac8 0x104fbc000 + 2677448
2 CubeLand 0x000000010525ab14 0x104fbc000 + 2747156
...
I don't know where the corresponding address value is, but I am checking it because it is considered to be an actor with that value when it is paused.
Thank you.
Loading images still are incorrect for the iPhone XR in universal build (Landscape) as per our messages last month. This was never resolved.
GAMESALAD DEV FOR HIRE! - www.gingagaming.com
Some iPads too.
Contact me for custom work - Expert GS developer with 15 years of GS experience - Skype: armelline.support
+1 @adent42
Check out my games on the App Store!
Wordgraphy / Polycolor / 20 Seconds / Minimal Maze
I have tried to resolve crash on ios13 for a month, but I don't know yet.
This is crash log file from apple. And attached.
Because of this crash, I can't update app. I need a help of GS team.
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0xfffa00010f283114
VM Region Info: 0xfffa00010f283114 is not in any region. Bytes after previous region: 18445055217124258069
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
MALLOC_NANO 0000000280000000-00000002a0000000 [512.0M] rw-/rwx SM=PRV
--->
UNUSED SPACE AT END
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [61645]
Triggered by Thread: 4
.....
Thread 4 name: Dispatch queue: com.apple.root.default-qos
Thread 4 Crashed:
0 CubeLand 0x000000010297c668 0x1026ec000 + 2688616
1 CubeLand 0x000000010297c9f8 0x1026ec000 + 2689528
2 CubeLand 0x000000010297c9f8 0x1026ec000 + 2689528
3 CubeLand 0x000000010297ca9c 0x1026ec000 + 2689692
4 CubeLand 0x000000010297ccc0 0x1026ec000 + 2690240
5 CubeLand 0x0000000102981054 0x1026ec000 + 2707540
6 CubeLand 0x0000000102979d44 0x1026ec000 + 2678084
7 CubeLand 0x000000010298ab14 0x1026ec000 + 2747156
8 CubeLand 0x00000001028b3560 0x1026ec000 + 1865056
9 CubeLand 0x00000001028b3654 0x1026ec000 + 1865300
10 CubeLand 0x00000001026fc7fc 0x1026ec000 + 67580
11 StoreKit 0x00000001d2862628 0x1d2850000 + 75304
12 libdispatch.dylib 0x00000001c3c5f610 0x1c3c04000 + 374288
13 libdispatch.dylib 0x00000001c3c60184 0x1c3c04000 + 377220
14 libdispatch.dylib 0x00000001c3c08758 0x1c3c04000 + 18264
15 libdispatch.dylib 0x00000001c3c14fd0 0x1c3c04000 + 69584
16 libdispatch.dylib 0x00000001c3c1579c 0x1c3c04000 + 71580
17 libsystem_pthread.dylib 0x00000001c3caff64 0x1c3ca4000 + 48996
18 libsystem_pthread.dylib 0x00000001c3cb2ae0 0x1c3ca4000 + 60128
....
Since it's a custom pause, do you do table stuff at that time? Crashes in GS games are almost always table related (referencing non-existant rows etc.) in my experience. While there's a good chance it's something beyond your control that GS will need to fix, I'd definitely explore that possibility thoroughly. Are you able to reproduce the crash yourself?
Contact me for custom work - Expert GS developer with 15 years of GS experience - Skype: armelline.support
It looks like it's trying to access a region in memory it doesn't have permission to access, or can't find because it was deallocated or doesn't exist.
I've never done this but you I've heard you can use xcode instruments and the "zombie objects" memory feature to hold the thread when it fails so you can see it in the history more readily.
https://medium.com/@pratheeshdhayadev/xcode-instruments-zombies-8b262b1ae9d8
Might be a good place to start.
Hmm good point! It is trying to reference something that doesn't exist, so that could be a table reference to a non-existant cell at runtime.
Follow us: Twitter - Website
just thinking along the lines of what @Armelline said about referencing things that don’t exist, i had issues with crashing on a recent test build because of this. it was linked to an unlocked actor using constrain in relation to an actor that wasn’t on that particular scene. may not help but just throwing it out there in case it does.
@Armelline Thank you very much.
Custom pauses are used extensively and are associated with multiple tables.
I have to look over there.
And now I can reproduce the crash. But no crash through viewer in ios13,
crash is occured only through flight test in ios13.
@AlchimiaStudios
I didn't exactly understand "trying to access a region in memory it doesn't have permission to access". Now a little understand. and thank you for the information about "zombie objects".
@bob loblaw
I will also check "linked to an unlocked actor using constrain in relation to an actor".
Thank you very much.
I'm still trying to track down a few other issues before I can divert to this issue, but we will have a new build this weekend that will hopefully fix the load image issues.