Closed phatlaunchdeck closed 3 years ago
Sorry I accidentally hit submit issue without finishing writing yet so I closed it but updated the post now.
Hey @phatlaunchdeck,
Is there a stack trace you could send us?
Hey @chshapiro, here you go, it's a pretty long stack trace so I can't comment it here and have put it onto another link: https://codeshare.io/5OD370
Forgive me if I should only get any specific part of it, I am not a native iOS developer so it's all pretty new to me.
Hey @phatlaunchdeck,
Unfortunately we haven't been able to repro this issue. Are you doing any customization for your in-app messages? Is this crash happening every time you display an in-app message or only sporadically?
I'm kinda positive that I did not do any customization to the IAM since the React Native doc indicates that the IAM will show up automatically. Oh one thing I forgot to mention that you need to test it with a real device to get the crash, it seems to work when I'm on simulators.
And yes, almost everytime the IAM shows up, clicking or swiping on any part of it will cause the crash to happen.
Hey @phatlaunchdeck,
Can you also turn on verbose logging and send us the logs from when you open the app until the crash occurs? If you're not comfortable posting them here, you can email them to support@braze.com.
Okay so I will turn that on, copy the stack trace as I did before and share with you via the email? Do I need to indicate any ticket number when I do that?
You can reference this issue. And please include the device logs as well as the stack trace in the email. Thanks!
Hey @chshapiro sorry to ask this, but I'm seeing a lot of logs for my device and not sure which one should I send to you guys? There are a few for today (May 13th) but as I see none is related to our app (Truckster) or saying Braze/Appboy or something.
Hey @phatlaunchdeck,
You can use these directions to get the logs follwing the steps in the Using Xcode
section.
I actually followed that page to get a device log, but seems like it was for an older version of XCode, there is no more "small arrow at the bottom left corner" on my XCode 12. However, I was able to retrieve the logs now, took a few hours for it to show up on my end.
Device Logs: https://codeshare.io/G6jAMp Stack Trace: https://codeshare.io/5egKNK
Hey @phatlaunchdeck,
Our team has potentially identified the issue. Do you have any UI element (first or third party) that could compete with Braze's in-app message window? We force our In-app message window to be key and visible when presented, it's possible that another UIWindow
in your code is doing the same thing, leading to the crash.
Hey @chshapiro, I have tried really hard to determine which library does that but all I can find in the whole node_modules is RCTLogBox and Alert, but they are core modules of React Native so those couldn't cause it right?
@chshapiro if it helps, I've just discovered that if I don't interact at all with the IAM and let it close itself after x amount of seconds, then it will not cause any crash.
Hey @phatlaunchdeck,
We're still unable to repro in our React Native sample app. Are you trying to show an alert at the same time that the in-app message is displayed?
@chshapiro I'm 100% sure that I do not do such. Last night when you asked me to look into whatever library doing "makeKeyAndVisible" I tried to remove everything from the screen that is suspicious from Modal to Toast (which is just a React Native View btw), but as soon as the Braze's IAM came in, it just crashed the app.
I even tried to bring out the IAM as soon as the app opens to avoid any possible libraries being loaded up and it still crashed the app.
@phatlaunchdeck we'll be in touch with your team to schedule a call
Fixed in Appboy-iOS-SDK 4.2.0.
Report
Describe your environment.
What did you do?
Test a campaign and got IAM sent to device
What did you expect to happen?
Tapping on the IAM should just simply close it
What happened instead?
The app crashed
Steps to reproduce
For IAM, I believe I did not need to do anything since on the React Native docs, they say everything is already in place.
Code Snippet
Are you doing any feature customizations that may relate to the issue? Can you share the code snippet?
No