There was a race condition when running the LP.start and creating the first activity of the application, because LP.start is starting a second thread to offload some of the heavy work. For that reason the wrapper is created in the same thread that the LP.start was called.
If you call LP.start(userId) with different userId the wrapper must be updated to comply with that. Previously this wasn't needed, because the wrapper factory uses the userId from APIConfig.
Background
There was a race condition when running the LP.start and creating the first activity of the application, because LP.start is starting a second thread to offload some of the heavy work. For that reason the wrapper is created in the same thread that the LP.start was called. If you call LP.start(userId) with different userId the wrapper must be updated to comply with that. Previously this wasn't needed, because the wrapper factory uses the userId from APIConfig.