This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| { | |
| "terminal.integrated.fontSize": 14, | |
| "workbench.iconTheme": "material-icon-theme", | |
| "workbench.startupEditor": "newUntitledFile", | |
| "editor.tabSize": 1, | |
| "editor.fontSize": 13, | |
| "editor.lineHeight": 25, | |
| "editor.fontFamily": "Fira Code", |
AlienDev66
/ my-readme.md
Last active
September 27, 2020 01:19
My readme.md all stuffed and with illustrations - README.MD complete.
AlienDev66
/ gist:59e7ecdc5a036ba72536015384f4dcad
Created
November 28, 2020 11:17
Setting a timer for a long period of time, i.e. multiple minutes, is a performance and correctness issue on Android as it keeps the timer module awake, and timers can only be called when the app is in the foreground. See https://github.com/facebook/react-native/issues/12981 for more info.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| I also had this bug, I was investigating, and then I came up with the solution that using expo will not solve, however, it can be hidden. | |
| Write this code snippet in the scope of your component, after the imports: | |
| LogBox.ignoreLogs(["Setting a timer"]); | |
| const _console = _.clone(console); | |
| console.warn = (message: string) => { | |
| if (message.indexOf("Setting a timer") <= -1) { | |
| _console.warn(message); | |
| } |