ThomasStubbe

Results 15 comments of ThomasStubbe

a timeToWait value of -1 (i.e. wait forever) is not a good default

I also agree with cuddlyporcupine. Waiting infinite is **not** a good solution! Not for a asynchronous client, not for a synchronous client. BTW, whether this code is executed synchronous or...

a timeToWait value of -1 (i.e. wait forever) is not a good default

I have an extra question for this. In my opinion this timeToWait is actually not a time-out. It only makes sense to use 1 or -1, where the 1 means...

Missing permissions required by intent Intent.ACTION_CLOSE_SYSTEM_DIALOGS:

I'm having the same issue... Adding `` to the AndroidManifest does not solve the problem... Also I do wish to target down to API level 21

Fullscreen control not updated after closing the native iOS fullscreen

I'm having the same issue. Is there any news on when the PR will be merged?

Fullscreen control not updated after closing the native iOS fullscreen

Also: onExitFullscreen is not triggered when leaving the iOS native full screen mode

why is it secure if i can access it from any apps?

@nerd2 this issue is not about physically-local attacks in general like the FAQ from chromium explains. The point is that any app that has access to the keychain can read...

Cannot add node "1" because a node with that id is already in the Store.

Or in case you use yarn: ``` "resolutions": { "react-devtools-core": "4.14.0" }, ```

How can one restart the library/stack with a similar effect to killing and restarting the app?

Hey, we have a similar question/issue. In some cases when the BLE devices goes out of range or the power is turned off, and goes back online/in-range soon after, the...

Failed to read PID file

I'm having the same issue on windows 10

Can't blacklist a subset

Did you manage to solve this with blacklists? I'm having the same issue. The createBlacklistFilter simply doesn't work. The README.md also says to use persistStore to pass the filter, but...