From 3f8af2deee128e21a34b11ae3830f85f21fea8ed Mon Sep 17 00:00:00 2001
From: Alex Kotliarskyi <alex.kotliarskyi@Oculus.com>
Date: Thu, 18 May 2017 16:58:46 -0700
Subject: [PATCH] Better context for "Calling JS function after bridge has been
 destroyed" warning

Reviewed By: AaaChiuuu

Differential Revision: D5091701

fbshipit-source-id: 9bf66cf35ffc3ade82a0ee61227760f0946d410d
---
 .../java/com/facebook/react/bridge/CatalystInstanceImpl.java   | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/ReactAndroid/src/main/java/com/facebook/react/bridge/CatalystInstanceImpl.java b/ReactAndroid/src/main/java/com/facebook/react/bridge/CatalystInstanceImpl.java
index 1ed7aaaef..d3a312b88 100644
--- a/ReactAndroid/src/main/java/com/facebook/react/bridge/CatalystInstanceImpl.java
+++ b/ReactAndroid/src/main/java/com/facebook/react/bridge/CatalystInstanceImpl.java
@@ -239,7 +239,8 @@ public class CatalystInstanceImpl implements CatalystInstance {
       final String method,
       final NativeArray arguments) {
     if (mDestroyed) {
-      FLog.w(ReactConstants.TAG, "Calling JS function after bridge has been destroyed.");
+      final String call = module + "." + method + "(" + arguments.toString() + ")";
+      FLog.w(ReactConstants.TAG, "Calling JS function after bridge has been destroyed: " + call);
       return;
     }
     if (!mAcceptCalls) {