Skip to content

chore: Add Additonal Diagnostic Logs#292

Open
BrandonStalnaker wants to merge 2 commits intomainfrom
chore/Add-Additonal-Diagnostic-Logs
Open

chore: Add Additonal Diagnostic Logs#292
BrandonStalnaker wants to merge 2 commits intomainfrom
chore/Add-Additonal-Diagnostic-Logs

Conversation

@BrandonStalnaker
Copy link
Contributor

Summary

A client is have a unique issue when publishing through .ipa builds.

Master Issue

Closes https://go.mparticle.com/work/REPLACEME

@BrandonStalnaker BrandonStalnaker force-pushed the chore/Add-Additonal-Diagnostic-Logs branch from 46b182c to 8a62c73 Compare March 13, 2026 18:38
@BrandonStalnaker BrandonStalnaker requested a review from a team as a code owner March 13, 2026 18:38
}

+ (void)load {
RCTLogWarn(@"[mParticle-Rokt] RNMPRokt module load");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One concern in using RCTLogWarn is that, this will show a yellow warning banner at the bottom of the screen when the app is running in debug mode. Other apps using the SDK may misinterpret this as a real problem.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's unfortunate, the problem with RCTLogInfo is it doesn't get shown in production builds,. The situation where the client is having problems.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implementing a workaround with os_log as the client dev has shown that to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants