Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"What do you dislike about React Native?" June 2019 Edition #134

Open
cpojer opened this issue Jun 12, 2019 · 67 comments

Comments

@cpojer
Copy link
Contributor

commented Jun 12, 2019

The React Native team at Facebook would like to collect a list of problems that people are experiencing on the latest versions of React Native (0.59 or 0.60). This was done six months ago in "What do you dislike about React Native?" and now it is time to get another pulse to understand what's causing problems for people. Today, we posted an update about React Native on our blog which tracks the progress we have made towards the top concerns from last time.

Please reply with all the issues that you are having with current versions of React Native, one comment at a time. Keep your descriptions short and ideally link to other places with more context. Feel free to mention not just technical things but rather any issue related to the React Native project. Add hashtags for easier categorization.

If something has been mentioned already, please use the upvote/emoji buttons instead of repeating the same thing so that it's easier to see how many people care about each issue. Please make one comment per topic so that people can upvote just one thing at a time.

Hypothetical Example:

Documentation needs more pictures of cats and dogs

When reading the React Native documentation I tend to get frustrated. Have you considered adding pictures of cute dogs and cats to make them more relaxing to look at? #documentation

Simple template with header (feel free to copy and paste)

### 

@RWOverdijk

This comment has been minimized.

Copy link

commented Jun 12, 2019

Live reload often causes issues

When using Typescript I have to reload my app often when using live reload. It does reload, but it shows the red screen with "Unable to find module for EventDispatcher". It has done this for a while. This combined with hot module reloading not working very stable causes some frustrations in dev. xcode also logs a lot of noise. There are plenty of issues about these things, too.

TL;DR; I guess for me it's #devExperience?

@jono-allen

This comment has been minimized.

Copy link

commented Jun 12, 2019

No documentation for adding build flavours for both platforms

Currently react-native only ships with debug and production builds. Quite often in a development stage, the use of multiple builds (Staging, QA, Sandbox) is beneficial. Would be an opportunity to better describe and add tools (maybe for the cli).

@jono-allen

This comment has been minimized.

Copy link

commented Jun 12, 2019

When adding native code warnings aren't clear that a new build is needed.

When adding a module. Often reloading the bundle the warnings can be confusing. I think like with react-native, a warning saying native modules are out of sync with a bundle or need a rebuild would be a good developer experience.

@jono-allen

This comment has been minimized.

Copy link

commented Jun 12, 2019

Imports are not from root.

When setting up a react-native project all imports are relative. It's very common that a developer will add babel-plugin-module-resolver. I would like to see this done in a way by default.

@jono-allen

This comment has been minimized.

Copy link

commented Jun 12, 2019

Cold start warnings.

React native doesn't have a friendly way to track down which modules are causing long startup times. I often struggle to track down these issues.

@AndreiCalazans

This comment has been minimized.

Copy link

commented Jun 12, 2019

Extend react-native cli to accept terminal commands

After starting the packager, I would like to be able to send commands to the running apps through the command line. It would be nice to accept commands for live reload, hot reloading, toggle debugger, and et cetera.

Doing so would improve developer experience, currently shaking the phone or using shortcuts to toggle the Dev Menu is a bigger hassle.

The available commands should be ideally displayed after you run react-native start

After dependencies are loaded:


Metro Bundler ready.

Loading dependency graph, done.

To hot reload press "r"
To restart the app press "R"
To toggle debugging mode press "d"

More commands could be included...

@ChuksFestus

This comment has been minimized.

Copy link

commented Jun 12, 2019

Expo!!!

Seriously the fact that you have to use expo to get this up and running is not cool. Don't get me wrong I like expo but it is usually very heavy so no matter how simple your app is, it will always be 20mb or more

@yinhangfeng

This comment has been minimized.

Copy link

commented Jun 12, 2019

Android JSC Crash

facebook/react-native#24261

@IljaDaderko

This comment has been minimized.

Copy link
Member

commented Jun 12, 2019

Assets for all resolutions are bundled with the app

Right now we can specify images for various screen resolutions by appending suffixes like @2x and @3x to their filenames. This gives benefit of performance on lower end / low res devices, but at the same time increases app size since all of these assets are included.

iOS solves this through combination of asset catalogs and bytecode enabled builds, where app store serves versions with correct image resolutions based on user device. (I'm not sure if android has something like this).

It would be awesome if we could still keep images in one place and use those suffixes as well as optimise our bundle / apk sizes.

@rebeccatownsend-rally

This comment has been minimized.

Copy link

commented Jun 12, 2019

Metro Symlinks aren't supported by default

We need symlink support to do a lot of things. For me, it's a major headache trying to to develop package dependencies and work with Lerna monorepos without this support. There are currently a few workarounds that the community has shared, but none are one-size-fits all, and it's a major time suck to finesse a fix that works for your specific use case. This should really be something that everyone can leverage out of the box.

@robertying

This comment has been minimized.

Copy link

commented Jun 12, 2019

Lean Core is great but extracted repos may not be well-attended

I believe Lean Core is a great idea. But I have seen some projects that were previously extracted become inactive. People can get responses quickly from the main repo but not from those repos residing in react-native-community.

Current disappointment:

@robertying

This comment has been minimized.

Copy link

commented Jun 12, 2019

Swift not being the default language for iOS

It would be much better for JavaScript programmers (at least for me) to quickly navigate through iOS source code written in Swift than Objective-C which lacks readability compared to the other languages (Java, JavaScript ...). Besides, many examples concerning iOS are now written in Swift. Encouraging Swift in RN projects can make it easier for developers to debug native code or make their own (common case: add custom logics into lifecycle functions).

I personally would like RN to:

  • change the default cli generated template from AppDelegate.m, AppDelegate.h and main.m to .swift implementations.

    Flutter cli does give you the option to generate Objective-C & Java template or Swift & Kotlin one.

  • encourage new community libraries to be written in Swift for iOS. Rewrite of existing projects would be awesome too!

@hrastnik

This comment has been minimized.

Copy link

commented Jun 12, 2019

Linking native modules

This is by far my greatest pain point. I know it's up to the developers of native modules to provide linking instructions and maintain the libraries, but I feel that there could be improvements there.
For example, if there was a mechanism exposed by react-native-cli that would enable maintainers a clean way to inject code and assets into the native project, it would make things much more consistent.
react-native link should do the trick, but in practice it fails more often than not, and running the command twice causes even more complications. Then we're stuck going through the module install docs, and fixing stuff line by line.
On Android it's mostly adding some permissions to the manifest, build.gradle, checking minSdk versions etc. A lot of that could be done programmatically if only there was an API exposed by rn-cli. For custom stuff like API Keys, custom configurations etc. an interactive shell could prompt the user to enter the needed data.

Shaking to get to dev menu

I'd love if there was an option to configure another way to get to the dev menu. Expo has a cool feature with having a menu in the notification bar. I wish this was the case with react-native init

@firofame

This comment has been minimized.

Copy link

commented Jun 12, 2019

Documentation on creating wrapper for iOS and Android SDKs would be great!

@iremlopsum

This comment has been minimized.

Copy link

commented Jun 12, 2019

This might not exactly be the feedback that you are expecting, but the fact that when child has elevation, and you animate alpha of the parent, the elevation alpha does not animate in Android P (facebook/react-native#23090). This requires me to constantly write hacks in my app and really is the thing that hinders me the most on a daily basis

@rakibtg

This comment has been minimized.

Copy link

commented Jun 12, 2019

Navigation Library

React Native doesn't have a proper native navigation library built in! It should have a native nav implementation where all of its animations etc could be on the main thread, dont have to block js thread.

@maleking

This comment has been minimized.

Copy link

commented Jun 12, 2019

Hot reloading

Hook incompatibility with hot reloader

@OwenMelbz

This comment has been minimized.

Copy link

commented Jun 12, 2019

Unify dev tooling between pure and expo

Currently the expo tool chain seems to have so much more love, not asking for expo SDK stuff, but simple things like the webpack config, debug menus, developer UIs with metro etc.

It’s so much nicer with expo and maybe sharing some of that sugar back to pure will be a nice addition ❤️

@esbenp

This comment has been minimized.

Copy link

commented Jun 12, 2019

Random build errors / lack of troubleshooting documentation

I very frequently run into random build errors like

Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_RCTSRWebSocket", referenced from:
      objc-class-ref in libReact.a(RCTInspectorPackagerConnection.o)
  "_OBJC_CLASS_$_RCTReconnectingWebSocket", referenced from:
      objc-class-ref in libReact.a(RCTPackagerConnection.o)
ld: symbol(s) not found for architecture arm64

etc. (see facebook/react-native#15838). The linked issue is almost 2 years old and I had this issue 2 days ago on 0.59.8. I assume this is some build step thing and not directly related to react-native as such but more on how its dependencies are handled by xcode/cocoapods or something, but to me this is the most annoying thing developing react-native. You end up spending far too much time trying to fix non-application errors like this. And I realize its hard for you guys to debug since its most likely very stateful and hard to reproduce, but I think there is a huge lack of troubleshooting/best-practice guides around building/running.

E.g. dealing with Cocoapods have been a huge pain for us. And the actual documentation about it is a small subsection of another topic (Integration with Existing Apps). I think a lot of react-native developers are confused about these things because we come from web. My first experience with xcode/cocoapods have been with react-native. There are no "this is how to set up cocoapods inside xcode, this is how to deal with common error a,b,c, this is how to reset everything when all else fails" etc. A lot of times it feels like you cannot develop react-native in the long run unless you are already skilled with xcode and the ios ecosystem

@brunolemos

This comment has been minimized.

Copy link

commented Jun 12, 2019

Hot reloading

Fix hot reloading to work reliably with hooks and state support.

It was one of the things that made me love react-native a few years ago and it's been broken for a while. I see Dan has been working on it which is super great, hopefully it gets released soon.

@suretarget

This comment has been minimized.

Copy link

commented Jun 12, 2019

Flatlist Component

There are 69 open issues related to this component (Some duplicated). Some issue related to Flatlist is opened since 2017. The bug is still present in the latest version. https://github.com/facebook/react-native/issues/16067
I wish the bug is fixed before releasing v0.60 stable. If we can resolve this component most of the issues is solved.

@diegolmello

This comment has been minimized.

Copy link

commented Jun 12, 2019

Slow TextInput is still a thing

facebook/react-native#20119

@brunolemos

This comment has been minimized.

Copy link

commented Jun 12, 2019

macOS support via Project Catalyst

iOS apps will be able to run natively in macOS. Currently the build doesn't pass. React Native only needs to make sure the build passes as the first step.

#131

@Doko-Demo-Doa

This comment has been minimized.

Copy link

commented Jun 12, 2019

FlatList performance

FlatList isn’t performant as it is advertised. It’s more like a workaround for long ScrollView. I was so hyped with Sophie’s blog post last year about Fabric and potential UICollectionView / RecyclerView interop, but it seems that it’s still not possible as of now

@iremlopsum

This comment has been minimized.

Copy link

commented Jun 14, 2019

@Jekiwijaya This is already a thing https://facebook.github.io/react-native/docs/scrollview#scrollto

But to piggyback on your comment. I would love the possibility to define decay values within a paginated scrollview when snapping. There is a decelerationRate prop, but it doesn't seem to do much for paginated scroll

@creambyemute

This comment has been minimized.

Copy link

commented Jun 14, 2019

Keyboard Handling

Even after over a year of working with RN I find myself as well a colleagues and a lot of ppl in the community struggling with handling Layout when the Keyboard is present.

There are so many libraries trying to solve this but I haven't seen a single example where it actually worked. It's always a finicky let's try that and then that library until you find one that works in the specific case...

If this could be included in the new documentation with a more extensive example than what is shown here: https://facebook.github.io/react-native/docs/keyboardavoidingview (which doesn't seem to work), that would be great I think

  • How to avoid keyboard in your layout (keep focused field visible)
  • How to focus next input field programmatically (through onSubmitEditing --> focus next field) without closing and reopening the keyboard (with tapping it works as we can just set keyboardShouldPersistTaps on a ScrollView)
  • How to scroll to next focused field correctly

The keyboard is a very important "component" but can "destroy" your layout and the docs aren't lending a helping hand there. So it'd be nice if beginners don't have to google for hours to find a working/acceptable solution.

If you see more points that could be covered let me know :-).

@rakibtg

This comment has been minimized.

Copy link

commented Jun 16, 2019

Depending too much on community effort

Don't get me wrong to begin with, community efforts makes a lot of thing possible today that revolutionized our society, including React Native.

However, When we love and use a framework that means we love it's consistency and the consistency of it's ecosystem, depending too much on community effort would cause frustration while development, and will hurt the concept of cross-platform development. There is lot of solutions today that either works on iOS or android which counteractive of being cross platform.

To uphold the situation one of the most popular module is react-native-push-notification by zo0r!! People already started to ask if it is abandoned being helpless there no other way but to use it.

Core app features that is a part of the app's ecosystem should be built in-house and then let the community to improve as they need them.

@Bessonov

This comment has been minimized.

Copy link

commented Jun 16, 2019

Usage of existing prioritization tools

There already tools, which can be used for prioritization of pain points:

@Bessonov

This comment has been minimized.

Copy link

commented Jun 16, 2019

Better TypeScript support

Same as 👻 Flow Typing NativeModules, but for TS.

@pvinis

This comment has been minimized.

Copy link
Member

commented Jun 17, 2019

Becoming its own thing, too far from the native platforms

React native started as a way to control native stuff like views, buttons, managers etc from javascript and react. For a while, it has been like that, and any new type of view or control etc has been implemented.

My fear is that maybe in the future RN will be something like other "multiplatform" tools, where they have their own layer of views or controls, completely abstracted from the native platforms it is underneath. I like the idea of having the Button. I like the idea of having Button with all the props available that could fit ios and/or android. I like the idea of a Button producing a simple native button on ios and a simple native button on android, even if they look different. I would be really sad if a Button would produce a button in both platforms that looks the same, but different to other native controls of each platform. Does that make sense?

Basically, I want RN to be a js/react layer juuuust above the native platforms, and I want to know that the native platforms are right underneath there, and I can play and manipulate them.

I don't want RN to be it's own rendering engine, replacing what native platforms have built. I don't want RN to be such an abstracted layer that I can't even see the native platforms hiding underneath it.

@simonedavico

This comment has been minimized.

Copy link

commented Jun 18, 2019

Starting with native modules is very hard

The docs section explaining how to create a custom native module are ok, but there is no guidance regarding setting up these modules as separate dependencies.

Third party projects like create-react-native-library and create-react-native-bridge are a starting point, but are not actively maintained.

Moreover, a beginner will find very hard to setup development environments for native modules (how to properly setup a project for developing the iOS/Android side of the bridge), what is the advised package structure, is it best practice to include a podspec and so on...

I feel that some guidance/tutorial/set of best practices included in the docs could be a start, but also having some command to scaffold correctly a custom native module would be great.

@ATShiTou

This comment has been minimized.

Copy link

commented Jun 19, 2019

Version updating is too frequent. And it is a disaster to upgrade for an old project with many third libraries.

I'm always out of date with the latest react-native version.But scared to upgrade it. And I do not think it is necessary to publish the new main version so frequently.

Basic framework problems are always ignored for years.

Custom JS component in some case can't receive event from native UI component. Issue 16122 and Issue 17646 are examples. This also happen on iOS when you drag several times quickly before it rebound. It is the reason why there is no a good third library to support customizing refreshing component in ScrollView or FlatList. The event which is ignored will destroy the user experience.

I have tried my best to support it via always sending onScroll event with extra data to JavaScript to resolve this problems. react-native-spring-scrollview

It is too slow to communicate with native modules on Android.

A native calling in JavaScript is more than 30ms delay. This is the reason why you can double click a button to navigate to two different screen with react-native-navigation. And it stops the ability on performance optimization in some special case, and stops high quality third libraries.

The worst gesture system I have used.

Now react-native-gesture-handler is a much better choice.

No optional import method

Any import or require is before compile. Can not support optional import.

@dayhaysoos

This comment has been minimized.

Copy link

commented Jun 19, 2019

React Native (FlatList) is not built to support Robust Spreadsheets

It's incredibly painful to do things like have a spreadsheet with bi-directional swiping to view data (horizontally and vertically). right now you have to nest FlatList in a ScrollView that is set to scroll horizontally which causes more problems if you wanted to style things in a very specific way.

Also, there should be a prop to make the left column a stickyHeader.

I know we've talked about this @cpojer, just want to see if there are others that have the same problems as me.

@dayhaysoos

This comment has been minimized.

Copy link

commented Jun 19, 2019

React Native needs better support for in-app-purchasing.

IAP is a very important aspect for mobile development, Bug Snag reports that MOST React Native apps are free:

https://www.bugsnag.com/content/state-of-react-native-2019

There are actually some helpful libraries out there (react-native-iap) but dealing with IAP is not very well documented in the React Native ecosystem in general. Perhaps this would encourage developers to make more money from their work or be taken more seriously by companies that plan on making money off mobile.

@tonmanayo

This comment has been minimized.

Copy link

commented Jun 19, 2019

ScrollView api

There are still many api's not available for Android on the Scrollview component.
contentOffset is still not available on Android and the workaround is a really ugly solution.
Please prioritize the Scrollview been truly cross platform as it is probably one of the most used components

@kelset kelset pinned this issue Jun 20, 2019

@huextrat

This comment has been minimized.

Copy link

commented Jun 21, 2019

Maintain and update toolchain

The toolchain is kinda complicated to use and is dependent on a lot of external tools that need to be synchronized between team members, something like Flutter does with flutter doctor would be easier to use.
Also, the process to update the react native version on an existing project is often very complex right now. Improve the process to update the native react version without breaking the whole project at each new version and without having to change files by hand will be a great improvement.

@jfrolich

This comment has been minimized.

Copy link

commented Jun 24, 2019

Integrate with SwiftUI and Jetpack Compose

It's very early but both Google and Apple have released declarative UI frameworks in the spirit of React (Native). Is it possible to leverage this for a future version of React-Native, or is there too much overlap in these framework and the React reconciler?

These platforms (especially Swift UI), allow you to create very concise UI's that are native and adapt to different apple platforms very well, and also make it very easy to add animations and gestures (above and beyond what's possible with React-Native). They also have first class support for navigation.

The only big advantage React-Native has over these platform is that it's cross-platform. And logic can be easily re-used in JavaScript. Can we have the best of both worlds?

@aksmfosef11

This comment has been minimized.

Copy link

commented Jun 24, 2019

Image nested within TextInput will be invisible in IOS

I want to create an app that uses custom emoji like Facebook, Slack, but IOS is currently unable to proceed because of the error.
facebook/react-native#18566

@Thioby

This comment has been minimized.

Copy link

commented Jun 26, 2019

Better support for debugging

Debugging RN application in long sessions is nightmare. Very often debugger has loaded different code than device.
Only one solution is restart bundler and the debugger.

@hey99xx

This comment has been minimized.

Copy link

commented Jun 27, 2019

State of JSC on Android

Yes, still even after 0.59 release. JSC on Android looks like something FB dropped the ball on, and now it's being carried by the community to large degree, but very slowly and unconfidently.

Previously when outside FB developers tried adding 64-bit support to old JSC in facebook/android-jsc#19 and facebook/android-jsc#30, they went ignored. As a solution one of these developers was allowed to check in a prebuilt JSC artifact into react-native, which was used in 0.58 release.

Maybe since FB was using their custom JSC build (as confirmed by an Expo maintainer on Reddit) this didn't disturb them. And even if this binary was totally safe (who knows?), FB let other apps using react-native to include a binary from an untrusted dev. This looks really insecure on behalf of FB in my opinion.

Right now RN is using JSC from react-native-community/jsc-android-buildscripts. Previously couple companies SoftwareMansion and Wix were heavily developing in this repo, but now it's a one guy called Kudo. Reading GitHub issues, it seems to me that the maintainers are visibly struggling to create a 64-bit performant and non-crashing JSC Android library.

Why isn't FB helping in that repo and in overall JSC and 64-bit ugrade issues more? It's ok that FB does not release its internal JSC modifications to opensource, but it doesn't look good in facebook/react-native#24261 with everyone on fire due to trying to build a stable RN app by August 1st deadline while relying on external devs to do the work.

@techday84

This comment was marked as off-topic.

Copy link

commented Jun 27, 2019

Facebook Ads shows blurry images on android device and when its happens the link does not work.

react-native-cli: 2.0.1
react-native: 0.59.4
https://github.com/unimodules/react-native-unimodules
https://github.com/expo/expo/tree/master/packages/expo-ads-facebook

Steps to Reproduce
I configure react-native-unimodules with expo-ads-facebook on a react native app.

On android device:

I can see the ad with the text but the image is blurred, when its happens the link doesn't work.
If the ad is a carrousel of images, the link works and the image is ok.

@brunolemos

This comment has been minimized.

Copy link

commented Jun 29, 2019

Concurrent mode

Currently we can play with Concurrent Mode on Web, but not on React Native. The release for web is planned for the next couple months (Q2 2019), but I haven’t noticed efforts on React Native specifically about it (which unfortunately affects react-native-web projects as well).

The article mentions it will wait React Fabric to be “near completion”, hopefully that is already the case.
Related issue: #4

Also, React Native’s code doesn’t pass the StrictMode check, which is required for Concurrent React. It is full of legacy apis like legacy context and unsafe methods like UNSAFE_componentWillReceiveProps.
Related issue: facebook/react-native#22186

@MohamadKh75

This comment has been minimized.

Copy link

commented Jul 13, 2019

Official docs for native modules in Kotlin and Swift

I guess it's better to have other versions of android native modules and iOS native modules that help the community to write a native module in Kotlin and Swift!
There are already a bunch of medium posts about it (that may be outdated).

@evan-richard

This comment has been minimized.

Copy link

commented Jul 23, 2019

Documentation and Support for Caching Images

The Image object in RN currently has the ability to prefetch images from a uri, however the documentation for this feature is seemingly limited. By implementing this feature in the example code, and even dedicating a section of documentation toward caching, the community may make use of native disk memory and see improved efficiency with faster image load times.

On caching, the addition of methods that help to:

  1. Remove specific entries from the disk
  2. Clear the cache
  3. Cache local images for faster retrieval

And the modification of the existing behavior:

  1. Changing the behavior of Image.prefetch for uris that are unknown at runtime
  2. Standardizing the behavior of Image.prefetch across iOS and Android

will grant more control for users that are currently caching images and help to decrease the number of times a cache miss occurs.

@Bessonov

This comment has been minimized.

Copy link

commented Jul 23, 2019

Documentation and Support for Caching

@evan-richard I've another proposal for caching. It would be better to have a general caching API, which can be configured to different needs, like limiting size on storage and/or number of entries wit differen strategies like LRU. Something like moize.

Also it should be possible to iterate over cache entries. For example, use smaller image from the cache, if bigger images isn't in the cache right now.

In regard of images or resources, which are visible only sometimes. They should interact with this cache and, for example, invalidate files which are not on the page at all (and not just invisible). Some sort of "purge priority".

@KrishnaKamesh

This comment has been minimized.

Copy link

commented Jul 25, 2019

Hi Upgraded React Native version from 0.59 to 0.60 after upgrading i am facing a big problem....
before the upgrading when i run react-native run-android directly js server had been started and app is installed all is well....But after upgrading when i run directly it is asking to run react-native start for starting metro bundler server for port..ok it is fine...but whe i run that command react-native start....after coming loading dependency graph... It is getting stopping there and the messge "done.." is also not getting and it is not moving further...I have tried in another mac system there also i am facing same problem..i am not getting solution anywhere...and it is working fine in Linux based system....could anybody help and resolve this issue..? Please...

it was nearly 30 min since i run react-native start but there is no any improvement..here is the screenshot
Screen Shot 2019-07-25 at 12 01 26 PM

@YajanaRao

This comment has been minimized.

Copy link

commented Jul 26, 2019

Support for Native File system access

React Native doesn't have a proper native file system access library built in!. Third party libraries are not maintained well.

@YajanaRao

This comment has been minimized.

Copy link

commented Jul 26, 2019

Support for Audio

Built in audio feature for react native would be helpful.

@ouabing

This comment has been minimized.

Copy link

commented Aug 1, 2019

Click and hold to select copy text

Text component currently doesn't support click and hold to select copy text. It's really an important feature for reading apps. We can use non-editable TextInput as a hacky solution, but there are still issues lying around (like nesting Text).

Issue here facebook/react-native#13938 .

@mjmasn

This comment has been minimized.

@ouabing

This comment has been minimized.

Copy link

commented Aug 1, 2019

@mjmasn facebook/react-native#13938 . Setting selectable=true can only copy but not select subset text on iOS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.