Elements upside down when adding library - iOS only
See original GitHub issueHi there,
We couldn’t find any solution or someone having a similar issue, so hopefully, you guys can help us out.
It seems that every time we include react-native-unity-view
, link files and include the UnityExport files, the react native elements turn upside down. We can fix a few screens by adding flexDirection: "column"
, but that seems too odd to be happening only in iOS.
Here is an example of our screen before including the files
And here is after
Any idea what to do?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:24
Top Results From Across the Web
Auto Layout Guide: Working with Constraints in Interface Builder
If you lay out your views using leading and trailing constraints, the views automatically flip positions when switching between left-to-right ...
Read more >cordova - How to disable orientation upside down for ios?
Then inside of Xcode need to disable the Upside Down option under the Device Orientation settings. enter image description here.
Read more >Managing Your Home Screen App Icons On iOS 15 - YouTube
Also learn how to create folders, change the order of the screens, and only show a small selection of apps on your Home...
Read more >Upside Down and Rotating iPhones - Use Your Loaf
The default is to build a Universal (iPhone + iPad) app, but this screen is as clear as mud. Why is the upside...
Read more >How to use iOS's App Library to organize your apps - The Verge
The new App Library in iOS 14 can be useful, especially if you tend to download a ... Choose either Add to Home...
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
@chiechelski This is going to sound absolutely stupid, but are you using Pods in your project and are you doing a
#include "Pods/Target Support Files/blah/blah.xcconfig"
at the top of your UnityConfig.xcconfig files? If so, try moving the include to the bottom of the UnityConfig instead, clean the project, and try a rebuild.@fluiddot I managed to make it work by changing the pods file include as mentioned above. By combining the two configs (unity and pods) together I was able to make it work. I have no idea what part of the ordering or inclusion process is causing it, but that’s what fixed it for me.