iOS Simulator cannot show Logs on Flipper
See original GitHub issue🐛 Bug Report
I use Flipper for my swift app, when I run the app on Simulator, I can’t see any Logs although Console log of xCode has value
To Reproduce
Click Button
@IBAction func toggleLogin() {
print("LOGIN TOGGLE")
NSLog("LOGIN TOGGLE")
}
Environment
xCode: latest 11.4.1 iOS SImulator: 13.4.1 Flipper 0.41.0 FlipperSDK 0.41.0 App: Swift 5.1, Cocoapods 1.9
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Troubleshooting General Issues - Flipper
If no app plugins are showing up, there may be a connectivity issue between Flipper and your app. Check connection issues to see...
Read more >Flipper Debugging for React Native - Povio
In this case, you often need to log messages, look out for device crashing, inspect network requests, and similar. However, Flipper is handy...
Read more >React Native 0.62 and Flipper Will Change Your Mobile ...
Flipper is a platform for debugging iOS, Android and React Native apps. ... using Flipper to reload or show the dev menu, no...
Read more >Issue with opening IOS Simulator | Apple Developer Forums
this is the correct way !! Open Xcode, then choose "Preferences..." from the Xcode menu (or press ⌘+,). Go to the Locations panel...
Read more >React Native 0.64 won't build iOS app after updating Xcode to ...
You should see text print out that says Fix: Pods/Flipper-Folly/folly/synchronization/DistributedMutex-inl.h, etc. If you don't, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the report! @priteshrnandgaonkar has confirmed that this seems to be affecting Swift apps at the moment. We’re looking into it.
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.