Branch Incident History

We have identified and resolved the issue affecting customers using NativeLink in our iOS SDK version 3.14.1 What Happened: In certain app launch scenarios, if a user had unexpected data copied to their clipboard, NativeLink could misinterpret it, potentially causing the app to crash. Who Was Impacted: This issue only impacted apps using NativeLink that were built on iOS SDK version 3.14.1. If your app does not use NativeLink, you were not impacted by this issue. How to Fix It: This has been fully resolved in iOS SDK version 3.14.2. If your app uses NativeLink, please have your engineering team update to this latest version to receive the fix. The Immediate Workaround (No App Update Required): If you cannot push an app update immediately, you can stop the crashes right away by disabling NativeLink in your dashboard.

We've identified the underlying issues and have released Branch iOS SDK v3.14.2, which includes a fix for the crash-on-launch issue impacting some apps using v3.14.1 under specific device clipboard conditions.If you are using Branch iOS SDK 3.14.1, we recommend updating to 3.14.2 to avoid any issues.

We are actively investigating an issue affecting some apps using Branch iOS SDK 3.14.1 where the app may crash on launch under specific device clipboard conditions.

We have identified and resolved the issue affecting customers using NativeLink in our iOS SDK version 3.14.1What Happened: In certain app launch scenarios, if a user had unexpected data copied to their clipboard, NativeLink could misinterpret it, potentially causing the app to crash.Who Was Impacted:This issue only impacted apps using NativeLink that were built on iOS SDK version 3.14.1.If your app does not use NativeLink, you were not impacted by this issue.How to Fix It: This has been fully resolved in iOS SDK version 3.14.2. If your app uses NativeLink, please have your engineering team update to this latest version to receive the fix.The Immediate Workaround (No App Update Required): If you cannot push an app update immediately, you can stop the crashes right away by disabling NativeLink in your dashboard.

We've identified the underlying issues and have released Branch iOS SDK v3.14.2, which includes a fix for the crash-on-launch issue impacting some apps using v3.14.1 under specific device clipboard conditions.If you are using Branch iOS SDK 3.14.1, we recommend updating to 3.14.2 to avoid any issues.

We are actively investigating an issue affecting some apps using Branch iOS SDK 3.14.1 where the app may crash on launch under specific device clipboard conditions.

This incident has been resolved.

At this time we believe that we have identified and addressed the root cause and all systems are back to normal. Webhooks and data availability are within SLA and normal bounds. We will remain in Monitoring through the weekend.

We are currently investigating an issue that began at approximately 7:30 PT, which is impacting our services. Webhook processing is currently exceeding our 30-minute SLA. Furthermore, data exports and data availability within our APIs are experiencing delays of up to four hours. We are actively working to identify the root cause and will provide further updates as more information becomes available.

As of 7:10 PT we are now processing webhooks within 30 minutes and we do not see delays with our attribution processing. We are monitoring the situation and continue to investigate for a root cause.

As of 7:10 PT we are now processing webhooks within 30 minutes. We are monitoring the situation and continue to investigate for a root cause.

We have identified a delay in attribution processing and webhooks. Processing is functioning correctly but currently delayed by approximately one hour. The Engineering team is investigating the underlying cause.

This incident has been resolved.

At this time we believe that we have identified and addressed the root cause and all systems are back to normal. Webhooks and data availability are within SLA and normal bounds. We will remain in Monitoring through the weekend.

We are currently investigating an issue that began at approximately 7:30 PT, which is impacting our services. Webhook processing is currently exceeding our 30-minute SLA. Furthermore, data exports and data availability within our APIs are experiencing delays of up to four hours. We are actively working to identify the root cause and will provide further updates as more information becomes available.

As of 7:10 PT we are now processing webhooks within 30 minutes and we do not see delays with our attribution processing. We are monitoring the situation and continue to investigate for a root cause.

As of 7:10 PT we are now processing webhooks within 30 minutes. We are monitoring the situation and continue to investigate for a root cause.

We have identified a delay in attribution processing and webhooks. Processing is functioning correctly but currently delayed by approximately one hour. The Engineering team is investigating the underlying cause.