iamjon

at 6 seconds you'll see the component load but there's not editor, it should look the way it does at 25 seconds in with the placeholder

@stulip I'm sorry I don't understand. Here is my component import React, { Component } from 'react'; import { View, StyleSheet, Keyboard, TouchableWithoutFeedback, Text, KeyboardAvoidingView } from 'react-native'; import {...

I didn't think of that. Good call. I'll have to investigate further. I think the following functions might help. The webview functions can be passed as props from the RichEditor....

So in my case it was being caused [this line](https://github.com/wxik/react-native-rich-editor/blob/42ec663a0392b48ce81496f539460363359d8345/src/RichEditor.js#L241) in RichEditor.js `const opacity = that.state.isInit ? 1 : 0; ` I used patch package and set the opacity to...

@stulip is this something you want to examine further or can I close the issue?

@FrancisLeigh we were dealing with a similar bug. If you download the latest version 6.0.7 it has a nice warning for this issue. I'd even mark this as closed.

This might help: https://github.com/ComputerWolf/SlickNav/issues/3

I can confirm the issue is happening. Turning off precise location also fixes. @NoahFace is there any difference between startUpdatingLocation and requestLocation in terms of the results that are returned?

This is the commit that re-introduced the error: 1f8e3942458d801c6f96fa06a9d45f35765b8d9f I also found this on stacked overflow that discusses startUpdatingLocation() vs requestLocation() https://stackoverflow.com/questions/39499541/cllocationmanager-requestlocation-takes-about-10-seconds https://stackoverflow.com/a/57372856 > TL;DR > requestLocation() is a convenient...