Intent order_intent = new Intent("com.clover.intent.action.START_ORDER_MANAGE"); order_intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);<br>order_intent.putExtra("com.clover.intent.extra.ORDER_ID", {ORDER_ID}); startActivity(order_intent);
Can you reproduce without your app installed? By just opening orders (simulating what your app is doing)?
@Jeffrey Blattman Seems it's okay without my app.
So, is something wrong with the way I call order app? I looked on another thread, people using the same code to call order app.
I'm wondering if the order app has some changed and our code need adjustment.
Your code looks fine but I can't see all of your code. Can you provide a link to the full logcat of when the problem occurs? Please use pastebin.com.
OrderConnector is thread safe. It can handle multiple requests at the same time.
Then it's strange.
After I separate the connector between task, no problem anymore.
Or probably more about the way I created the task.
Other than separating the connector, also there was a change on the way our task created.
We already submit the new app, hopefully, our beta tester doesn't see any issue anymore.
2 People are following this question.