Bug iOS v4.1.0

MadScience2006

New member
Oct 5, 2012
779
0
This thread is for posting bugs & issues for iOS v4.1.0 ONLY (new bugs as well as lingering issues that haven't been fixed). If you want to post general feedback or comments, then please use THIS THREAD instead.

When posting a bug, please use the following format:

Device/OS:

Bug Description:

Steps To Reproduce:

Frequency:

Additional Comments:


Please also remember to email any bugs you find to support@pinballarcade.com

Thank you!
 
Last edited:

MadScience2006

New member
Oct 5, 2012
779
0
Device/OS: iPhone 5 on v8.1 beta 2, iPad 4 & iPad mini 2 on v7.1.2

Bug Description: Pin*Bot table crashes TPA to the main menu (SpringBoard) after the completion of a game.

Steps To Reproduce: Start a game of Pin*Bot, then let all balls drain

Frequency: 100%

Additional Comments: All iDevices are affected AFAIK. Crash is 100% reproducible, 100% of the time
 
Last edited:

RSchwantner

FarSight Employee
Aug 4, 2014
239
0
Device/OS: iPhone 5 on v8.1 beta 2, iPad 4 & iPad mini 2 on v7.1.2

Bug Description: Pin*Bot table crashes TPA to the main menu (SpringBoard) after the completion of a game.

Steps To Reproduce: Start a game of Pin*Bot, then let all balls drain

Frequency: 100%

Additional Comments: All iDevices are affected AFAIK. Crash is 100% reproducible, 100% of the time

Are you up to date? There should be a patch in the latest version.
 

MadScience2006

New member
Oct 5, 2012
779
0
Are you up to date? There should be a patch in the latest version.
Yes, v4.1.0. I believe one of the recent patches applied to BRIDE of Pin*Bot which had the same crash symptom which is now corrected. The crash to Springboard (from a few versions back) is still affecting Pin*bot.
 
Last edited:

9u1d0

New member
Jan 7, 2013
310
0
Device/OS: ipad air/ios7

Bug Description: Creature Black Lagoon, high scores above 10B not registered in table High Score list, you may not even enter your initials at all.

Steps To Reproduce: well, score over 10B (roll over) and you will see.

Frequency: eh, I guess always, might be a rom issue
 
Top