Jetpack compose can not inspect in AS Layout Inspector.
Is there any tools can inspect compose layoutnode.
After Enabling Enable View Attributes in Device's Developer Options solved the issue for me in Android 12 Device
As of the Jetpack Compose Beta launch, the latest version of Android Studio has a version of the Layout Inspector that supports inspecting jetpack compose layouts:
https://developer.android.com/jetpack/compose/tooling#layout-inspector
Android Studio's Layout Inspector does not currently support Compose. Until then you can use Square's Radiography for debugging, which will print your view hierarchy.
Check out the documentation to use it with Compose: https://github.com/square/radiography#jetpack-compose-support
For me, I have to do this to make LayoutInspector works with Compose (Enabling Enable View Attributes in Device's Developer Options doesn't work).
// Before
packagingOptions {
resources.excludes.add("META-INF/*")
}
// After
packagingOptions {
// resources.excludes.add("META-INF/*")
}
It's mentioned in the Google issue tracker. The quote from the user comment:
On my project, i had a similar issue where the layout inspector was not working (the compose views where not shown). I solved it removing this line in my build.gradle :
packagingOptions {
resources.excludes += setOf(
"META-INF/*.version", <= Removing this line
"META-INF/proguard/*",
"META-INF/*.kotlin_module",
"META-INF/DEPENDENCIES",
"META-INF/AL2.0",
"META-INF/LGPL2.1",
"META-INF/*.properties",
"/*.properties"
)
}
Question is not very clear. If I understand it correctly, may be you are not seeing your app in the Select a process option of the Layout inspector.
https://developer.android.com/studio/debug/layout-inspector#inspect-compose-semantics
Make sure your app is using an API level of 29 or higher, and Compose
1.2.0-alpha03 or higher. Then, deploy your app as you normally would.
Related
On web, the order is just fine, but on mobile everything is swapped: the order of the components, left margins are right margins etc.
I did not change anything on purpose. From one build to another, the order simply changed.
I attached a screenshot from one of their templates which shows the same behavior (so the problem is not restricted to a single project):
screenshot from react-native template ios application
Thank you!
Update:
code: https://github.com/expo/examples/blob/master/with-tab-navigation/App.js
image: screenshot from mobile phone ios
I also checked with another phone and it shows the proper order. Could it be related to some language or region?
Flexbox works the same way in React Native as it does in CSS on the web, with a few exceptions. The defaults are different, with flexDirection defaulting to column instead of row, alignContent defaulting to flex-start instead of stretch, flexShrink defaulting to 0 instead of 1, the flex parameter only supporting a single number.
https://reactnative.dev/docs/flexbox
I uninstalled my Expo Go application from mobile and reinstalled it from App Store. Works now
I'm using Xcode 11.3 alongside MacOS 10.15.2. Even though the project settings are correctly set to New Build System, the orange hammer is still present in the activity view as pictured below.
According to this doc that means
Projects configured to use the legacy build system will display an orange hammer icon in the Activity View.
This stops me from being able to use Swift Package Manager. I get an error stating Packages are not supported when using the legacy build system, but the current workspace has it enabled.
I've attempted to reinstall Xcode multiple times already with no luck. This happens for new projects and workspaces also. There doesn't appear to be a lot about how to manage this elsewhere.
Any ideas ?
The codebase I was using had some setup steps which included
defaults write com.apple.dt.Xcode UseModernBuildSystem -bool NO
This affected any new projects that I created. Setting this to YES solved my problem.
I am working on a project where we need to provide localisation support - (Localisation is provided based on user choice not based on System Settings. ). I have provided localisation support in storyboard and base localisation is also provided.
I was able to get the strings in TextFiled localised using the below code
var languageBundle =NSBundle.FromPath (resourcePath);
var storyborad = UIStoryboard.FromName ("MainStoryBoard", languageBundle);
storyborad.InstantiateViewController ("ViewController");
But the images are not shown at all irrespective of language.
I have placed all my images directly in the Resource folder.
Is there any way to show the images ? Is am missing any information that need to added in the bundle when initiating the story board.
I am new to iOS Development.
I was not able to get exact solution to this problem but i was able to do a workaround. Placing images under the respective locale folder could resolve this issue.
I am using Xamarin studio for development so when i added the required images as links, some times it shown a positive result.
I am developing an application with jquerymobile. I want to disable my landscape orientation for only main page not for others. Are there any commands to do this for pages separately instead of manifest file?
For Android, you can use this screen orientation Phonegap plugin in your main page. I've updated the code to be compatible with Phonegap 2.8.0 - you can find the source code in my answer to this question as well my Eclipse project and resulting APK.
There's an equivalent iOS plugin here but I haven't used it and it may need updating for use with the most recent versions of Phonegap.
I use jQuery Mobile with HTML5 and CSS3.
When I upload my code to PhoneGap cloud build servers and place the app on my iPhone and start the app, I see the following splashscreen:
The question now is: how can I override this image?
Do note: I'm not using a regular phonegap project (e.g. in Visual Studio), but just an index.html file with js and css files.
Thanks!
You can get some valuable information from here. This is from official Phonegap team. Also you can look into this too.
Hope it helped you.
Apple now requires a splash image. So if you don't include one in your config file on Phonegap Build, then the compiler inserts that ugly default version for you. So the solution is to make sure that you use your own custom splash image and specify that custom image with appropriate settings in the config file. You should be fine after that.
https://build.phonegap.com/blog/new-apple-app-store-submittal-rules
If a splash screen is not found in your package the PhoneGap default
image will be used, so be sure to include your splash screen in all
the required dimensions for your device. Apple has a handy guide to
these dimensions here.