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
RCTAppSetupPrepareApp breaks Flipper support on iOS #33497
Labels
Impact: Regression
Describes a behavior that used to work on a prior release, but stopped working recently.
Needs: Attention
Issues where the author has responded to feedback.
Platform: iOS
iOS applications.
Resolution: Locked
This issue was locked by the bot.
Shared with Meta
Applied via automation to indicate that an Issue or Pull Request has been shared with the team.
Tool: Flipper
Comments
cortinico
added
Impact: Regression
Describes a behavior that used to work on a prior release, but stopped working recently.
Needs: Attention
Issues where the author has responded to feedback.
Tool: Flipper
Shared with Meta
Applied via automation to indicate that an Issue or Pull Request has been shared with the team.
and removed
Needs: Triage 🔍
labels
Mar 25, 2022
cipolleschi
pushed a commit
to cipolleschi/react-native
that referenced
this issue
Mar 25, 2022
Summary: This DIFF turns on the `FB_SONARKIT_ENABLED` flag when installing Flipper ina RN app. The flag is enabled only in Debug config, given that Flipper is installed only in this configuration. This PR also fixes this issue: facebook#33497 ## Changelog [iOS][Changed] - Enable SonarKit in React-Core when the configuration is `'Debug'` Differential Revision: D35141506 fbshipit-source-id: 019bab85d60b2b02ac50fcc82de7879833653505
facebook-github-bot
pushed a commit
that referenced
this issue
Mar 25, 2022
Summary: Pull Request resolved: #33499 This DIFF turns on the `FB_SONARKIT_ENABLED` flag when installing Flipper ina RN app. The flag is enabled only in Debug config, given that Flipper is installed only in this configuration. This PR also fixes this issue: #33497 This PR is required because release 0.67 has the Flag in the app, while release 0.68 moved it in the React-Core pod. We can't enable the flag at the `React-Core.podspec` level because we should not make assumptions on whether users want flipper or not. ## Changelog [iOS][Changed] - Enable SonarKit in React-Core when the configuration is `'Debug'` Reviewed By: cortinico Differential Revision: D35141506 fbshipit-source-id: 171b7fa8ea7727c633ef963408e86b332c32e9fa
ShikaSD
pushed a commit
that referenced
this issue
Mar 25, 2022
Summary: Pull Request resolved: #33499 This DIFF turns on the `FB_SONARKIT_ENABLED` flag when installing Flipper ina RN app. The flag is enabled only in Debug config, given that Flipper is installed only in this configuration. This PR also fixes this issue: #33497 This PR is required because release 0.67 has the Flag in the app, while release 0.68 moved it in the React-Core pod. We can't enable the flag at the `React-Core.podspec` level because we should not make assumptions on whether users want flipper or not. ## Changelog [iOS][Changed] - Enable SonarKit in React-Core when the configuration is `'Debug'` Reviewed By: cortinico Differential Revision: D35141506 fbshipit-source-id: 171b7fa8ea7727c633ef963408e86b332c32e9fa
douglowder
pushed a commit
to react-native-tvos/react-native-tvos
that referenced
this issue
Mar 25, 2022
Summary: Pull Request resolved: facebook/react-native#33499 This DIFF turns on the `FB_SONARKIT_ENABLED` flag when installing Flipper ina RN app. The flag is enabled only in Debug config, given that Flipper is installed only in this configuration. This PR also fixes this issue: facebook/react-native#33497 This PR is required because release 0.67 has the Flag in the app, while release 0.68 moved it in the React-Core pod. We can't enable the flag at the `React-Core.podspec` level because we should not make assumptions on whether users want flipper or not. ## Changelog [iOS][Changed] - Enable SonarKit in React-Core when the configuration is `'Debug'` Reviewed By: cortinico Differential Revision: D35141506 fbshipit-source-id: 171b7fa8ea7727c633ef963408e86b332c32e9fa
Resolved in 0.68.0-rc.4 👍 |
Saadnajmi
pushed a commit
to Saadnajmi/react-native-macos
that referenced
this issue
Jan 15, 2023
Summary: Pull Request resolved: facebook#33499 This DIFF turns on the `FB_SONARKIT_ENABLED` flag when installing Flipper ina RN app. The flag is enabled only in Debug config, given that Flipper is installed only in this configuration. This PR also fixes this issue: facebook#33497 This PR is required because release 0.67 has the Flag in the app, while release 0.68 moved it in the React-Core pod. We can't enable the flag at the `React-Core.podspec` level because we should not make assumptions on whether users want flipper or not. ## Changelog [iOS][Changed] - Enable SonarKit in React-Core when the configuration is `'Debug'` Reviewed By: cortinico Differential Revision: D35141506 fbshipit-source-id: 171b7fa8ea7727c633ef963408e86b332c32e9fa
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Impact: Regression
Describes a behavior that used to work on a prior release, but stopped working recently.
Needs: Attention
Issues where the author has responded to feedback.
Platform: iOS
iOS applications.
Resolution: Locked
This issue was locked by the bot.
Shared with Meta
Applied via automation to indicate that an Issue or Pull Request has been shared with the team.
Tool: Flipper
Description
In the latest RCs of RN 0.68.0 (tried 2 & 3) Flipper setup has moved into the
RCTAppSetupPrepareApp
helper. This effectively breaks integration as in this fileFB_SONARKIT_ENABLED
is not defined nor is the Flipper dependencies available as they are not listed in theReact-Core
podspec.Copy-pasting the setup into the AppDelegate as it works in 0.67 and below restores the functionality.
Version
0.68.0-RC.3
Output of
npx react-native info
Steps to reproduce
Observe no application selectable:
Snack, code example, screenshot, or link to a repository
No response
The text was updated successfully, but these errors were encountered: