I did a reset (and re-download of the skins) in one app, but now my other app fails with this message:
Failed loading the skin file: /iPhoneX.skin
I have downloaded the iPhone.skin in the other app (I realized the old iPhoneX skin I had didn't support the safeArea).
The Simulator won't start with this issue, and despite searching, I haven't managed to figure out how/where to fix it.
Not sure if the "/" before the skin name is what is causing is the problem?
Related
I am starting to help someone with a new project. This project is React (React Native as is a mobile app).
The project is working fine on her laptop (in her browser), and when I scan the Expo QR code, the app works fine on my Android device.
However, trying to run it in my browser is throwing all these errors:
The 'Can't resolve' error doesn't make sense, because the correct react native files are there. Is this a cache problem? I have tried deleting the .expo/web/cache folder and starting over.
Also, why are there multiple errors in my console, but only one being shown in the information on the actual web page? Does this mean that the single error being shown is causing all the other errors, or it is the only one which needs fixing, or will it show the next error when I fix the one that is being shown?
Thanks
Seems to have been a known problem re babel. See the links below:
https://github.com/babel/babel-loader/issues/173
how to solve this error You may need an appropriate loader to handle this file type
After installing the module H5P, my site wouldn't load and only displayed "Error" The website encountered an error, please try again later
I had to manually disable the H5P modules in the database then clear the cache and a few minutes later the website started loading again. It also seems as if sub-domains couldn't load during this time.
Has anyone else experienced this?
After uninstalling and deleting the H5P module, it still shows on the page: admin/config/system/h5p but when the H5P link is clicked I get a Website encountered an error, please try again later error.
I can't seem to clear the cache via the site admin and I can't save panel pages. It says saved but when i try to access the page url, it says page not found.
Someone else said "I've had the same or similar issue. When I install, I just get a WSOD. I ended up using the missing module cleaner to get my site back to working normal after manually uninstalling it."
I've installed the module missing fixer module and when I enabled the module I got a "Website encountered an error, please try again later error." message but when I refresh the page, it shows the module is enabled.
However, when I click on "configure" from the module list page, it takes me to /admin/config/system with no option to configure the settings or actually use the module.
Should I be looking in the database for something that could fix this issue?
This issue was fixed by truncating every cache_ table in the database.
ERROR ITMS-90023: "Missing required icon file. The bundle does not contain an app icon for iPad of exactly '167x167' pixels, in .png format for iOS versions supporting iPad Pro."
Hi got the above message when try to submit built IPA file, using Mac's Application Loader..
Can anybody advice how to overcome this? I try to unzip that IPA file and found there is no 167x167 icon file for ipad. I try to create one and zip it back, but I got another error said "Invalid Signature" when try to resubmit using that "cheat" ipa file... should this 167x167 ipad icon file build by the codenameone build server as well?
Kindly advice.
You can't modify the IPA after it's generated. This will break the signature. The icon also needs to be listed in a couple of places for it to work properly.
I've added this new 167px icon to the icon list so with the update tomorrow (Feb 9th 2018) it should "just work" for new builds.
Also notice that at this time only the standard build works properly for submission and we haven't yet tested the new 9.2 builds. It's also important you use Application Loader for upload and not xcode as that might break things.
When I try to run my app on the emulator in Smartface App Studio, I get an error. It so interesting, i tried something to fix it and googled to find a solution lots of times. But i got nothing.
Checking Android SDK Configuration.Searching for Devices...Device found: Faea HY509SGenerating Exporting Packages for Android profile:"Default"Pages, JavaScripts files are preparingProject resources are preparingDatasets are preparingInstallation packages are creatingInstalling Emulator...Application could not install toError Message : pkg: /sdcard/SmartfaceEmulator.apkFailure [INSTALLFAILEDCONTAINER_ERROR]
Same issue again? Please refer to Troubleshooting document!Sorry, an error occured during launching! Please try to launch from your device.
The problem is about Manifest configuration.
I guess you changed some part of it.
There is a manifest entry like android:installLocation
it should be auto like;
android:installLocation="auto"
Smartface.io Team
To my iPhones app's XCode project I have added the following launch images:
Default~iphone.png
Default~iphone#2x.png
Default~iphone-568h#2x.png
On the iPhone4, iPhone4s and iPhone5 the correct launch image is shown.
Also XCode's project summary tells me that every thing is ok with the launch images.
But if I launch the app on my iPod4 then the iPhone5 splash screen (Default~iphone-568h#2x.png) and not the iPhone4 screen (Default~iphone.png) is shown. There is iOS6 installed on my iPod.
Any idea, what's wrong here?
The files above have wrong names. They should be:
Default~iphone.png
Default#2x~iphone.png
Default-568h#2x~iphone.png
But giving the files the right names is not enough. You should:
Look into the info.plist file of your app, that there are the right launch images set
The wrongly named image Default~iphone-568h#2x.png can remain in the application bundle, even if you delete and reinstall the app. Thus it can be that the changes above have no effect.
To prevent this I had to delete my app, clean and recompile my XCode project and reboot my device. After that everything worked fine.