App crashes at end of chapter 1

By SteveMarroni, in The Lord of the Rings: Journeys in Middle-earth

Is anyone else running into this problem? Right after we finished Chapter 1 (and lost), instead of going to the campfire scene, the app crashed. I tried a few times, and it crashed each time after giving the end-of-the-chapter text.

Is it my device, or are other people having problems, too?

I have only played the first chapter once, but I didn't experience any issues with the app.

Same here, no problems for me. I played it on Steam. What OS are you running it on?

I downloaded it from the Apple store, and I'm playing it on my iPad Mini 2. It's a bit of an older iPad, but it has the latest operating system. I never have problems running Mansions of Madness on this device.

i have a mini 3 at home i can try to see if i can replicate the problem

It crashed on my ipad pro

I did get an email back from the company asking for more information to pass on to their developers. Hopefully soon they'll let me know if it's on my end or if it's some bug they have to fix. We had a blast playing the game until it crashed.

I tried it on my iPhone, which is much newer than my iPad, and it worked. So the app must not work on older iPads.

Thanks for your feedback, everyone.

Runs like a dream so far on my iPad

No problems on the iPad and looks great.

Crashed for us at the exact same point. Using iPad Pro, iOS 12.2

Hello everyone!

We are currently looking into this issue but have had no luck reproducing it on our end.

It appears to be happening to iOS devices only. We have tested it with many devices, including ones that have been listed in this thread (iPad Pro and iPad Mini 2) without experiencing any crashes/errors.

At this time we're asking for any more information you may have that will help us track down the issue:

  • What Device(s) are you using? What operating is installed?
  • What version of the app is installed?
  • At exactly what point does the crash occur?
    • From what I've gathered, it happens when transitioning from the Game scene (end of mission) to the Map scene.
  • What was the result of the first mission? Win, Loss, Player Last Stand, etc.
  • Number of players in the campaign?

Any and all additional information is welcomed, including hearing from those who are NOT experiencing the issue.

I will monitor any responses to this thread; Also feel free to reach out directly at [email protected].

Thanks

Edited by FFG_Software

This happened to me: iOs 12.2 on an ipad 6. The app is fully updated as of today. This was a 4 player game that ended in defeat. Restarting the app and iPad has had no effect, crashes every time right after awarding lore and experience after the loss. I noticed that when I reload the game, the screen is off-center - I am looking at a nearly blank screen and the map is just visible to the right of the screen. I have to scroll over to re-center it.

I do have a separate campaign going where this did not happen - 3 player game, scenario 1 ended in victory.

But I am hesitant to continue playing until I can get the 4 player campaign problem fixed.

Any ideas?

Good News!

With the help of further email reports and forum posts, we were able to identify this elusive bug!

v1.0.4 is on it's way to each platform, and contains a hotfix specifically for this issue. This update will not disrupt any save files, and players should be able to pick up right where they left off and finish Chapter 1 without crashing.

chrashed on cromebook today. chapter 2. game vers 1.0.5.

tried to reboot CB but no effect

Cromebook is running version 74.0.3729.159 (Officiel version) (64-bit)

app froze, the shut down threw the intire chapter

we had to quit and save all the time

On 6/22/2019 at 4:24 PM, Lundsvig said:

chrashed on cromebook today. chapter 2. game vers 1.0.5.

tried to reboot CB but no effect

Cromebook is running version 74.0.3729.159 (Officiel version) (64-bit)

app froze, the shut down threw the intire chapter

we had to quit and save all the time

Did you send an email to the address above? I only suggest it because they may have stopped monitoring the thread after the initial issue was fixed in 1.0.4.