No callback from getApplicationInfo sdk 2.1

Seems like this problem has reappeared or no one has tested this behavior in a way I did.

Problem: if there are at least two of the companion applications on on phone talking to two different applications with their own app ID's on watch respectively, then in the same phone reboot cycle first application launched will work fine, but the second one won't receive getApplicationInfo callback for the first time it'll try to acquire ConnectIQ instance, even more unexpected is the fact that the first application if it's still running will receive this callback instead. This will happen only once for the second app: if it's started for the second time, then callback will be received.

I discovered this by running a widget on phone, which acquires ConnectIQ instance and keeps it during it's lifecycle. This widget is still in development therefore it has a rather extensive logging system. I noticed, that after I added widget to the home screen, it sent info to the watch, then I started another one of my applications, which is the companion app and instantiates ConnectIQ on start releasing it on exit. Strangely enough, at the same time I received getApplicationInfo callback with the widget app ID in my widget, the companion app didn't receive this callback and was unable to send data to watch until I force closed and restarted it. For the second time ConnectIQ instance was initialized correctly and no fake callback was given to previous application. If I delete widget from the home screen and add it once again, then this time widget won't receive getApplicationInfo callback for the first time it tries to initialize connection despite previously run twice companion application is already closed.

Therefore I consider, that current implementation of Android BLE SDK doesn't reinitialize some variables during instantiation and keeps traces of the previous connections. The only workaround I found so far is to start a timer/handler to wait for a set amount of time (e.g. 30 seconds) and if getApplicationInfo callback is not received before timer expires, then I shut down and restart ConnectIQ connection, which helps to initialize the connection correctly. This is identical to acquiring ConnectIQ instance twice sequentially, but the timer solution seems to be more appropriate choice to me in this situation.

If someone from Garmin development team will check this thread, then please, let me know whether additional info is needed for this problem to be transferred to GCM team.
Thanks in advance.