I get the following error when building after changed the mac machine(I'm using VMWare and created new machine to use the latest OS version)
I copied the xcode project from old machine to the new one.
Severity Code Description Project File Line Suppression State
Error 2019-12-16 04:09:43.959 ibtoold[1526:26675] DEBUG: Added to
environment: {
TMPDIR = "/var/folders/xn/r2znrb712jl3558nqh0000gn/T/1AA1234D-4B58-5555-6665-52BC1709F584";
} 2019-12-16 04:09:45.057 IBCocoaTouchImageCatalogTool[1549:27672]
Unable to get image dimensions for
file:///Users/user/Library/Caches/Xamarin/mtbs/builds/ExpoUp.iOS/xxx/obj/iPhone/Release/actool/cloned-assets/Assets.xcassets/AppIcon.appiconset/Icon-App-20x20#1x.png
2019-12-16 04:09:45.076 IBCocoaTouchImageCatalogTool[1549:27672]
CoreThemeDefinition: Unable to create image for
file:///Users/user/Library/Caches/Xamarin/mtbs/builds/ExpoUp.iOS/xxx/obj/iPhone/Release/actool/cloned-assets/Assets.xcassets/AppIcon.appiconset/Icon-App-60x60#2x.png
Related
After updating to VS 17.3.6 (Xamarin.iOS Version: 16.0.0.72) I'm getting the following error when trying to build the app for the Simulator. It does work on a physical device.
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.Shared.targets(3,3): Error: No matching framework found inside '/Users/xxx/Library/Caches/XamarinBuildDownload/FAdM-8.13.0/Frameworks/GoogleMobileAdsFramework-Current/GoogleMobileAds.xcframework'.
SupportedPlatform: 'ios', SupportedPlatformVariant: 'simulator', SupportedArchitectures: 'i386, x86_64'.
I've tried deleting the obj and bin folders.
How can I solve this issue?
I would like to pull the neo4j image on my Mac Book M1 machine.
The dockerfile is something like this
FROM neo4j:3.5.30-community
....
If I don't specify the target platform it gave me an error on pull :
=> ERROR [internal] load metadata for docker.io/library/neo4j:3.5.30-community 0.6s
------
> [internal] load metadata for docker.io/library/neo4j:3.5.30-community:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: no match for platform in manifest sha256:a3c8ec959f11ecac3e90c6c032afb217718128366b6ba3d59cf55ad6320be8d1: not found
ERROR: Service 'designer-neo4j' failed to build: Build failed
I google it a bit and I found that I need to do a:
export DOCKER_DEFAULT_PLATFORM=linux/amd64
This works and image is pulled and it runs - slow and with a lot of crashes...
Inside my docker dashboard, it warns me with a red exclamation mark: amd64: Image may have poor performance.... If I google it tells me, that I should have arm64 architecture images...
So how to pull the neo4j image on mac m1, so that it will work?
You need to use a more recent version of Neo4j, 3.5 is EOL already.
If you do use 4.3 or 4.4 you will be able to simply pull arm64 compatible images.
Check on docker hub https://hub.docker.com/_/neo4j?tab=tags&page=1 , you will see immediately the image tags compatible with arm64 architectures.
When I'm trying to deploy (any) Windows Phone 8.1 error I get the following error in VS2013:
Error 3 Error : DEP6100 : The following unexpected error occurred during boostrapping stage 'Downloading package 'FF63DEA8-0A0C-4E52-B20F-84F390C30F32'':
DirectoryNotFoundException - The system cannot find the path specified.
And in VS2015:
Show Details Severity Code Description Project File Line
Error Error : DEP6100 : The following unexpected error occurred during bootstrapping stage 'Downloading package 'EB22551A-7F66-465F-B53F-E5ABA0C0574E (NativeMsVsMon)'':
DirectoryNotFoundException - The system cannot find the path specified.
I can deploy the app in Visual Studio 2013 , but in my case this is not an option because VS2013 does not support universal applicationss, so I can't open my project.
Phone is recognized by my computer, it is unlocked, I've tried resetting import export settings.
I have VS2013 update 4.
I was facing the same issue. Don't know if this is related to your issue but I've discovered that all the mess was generated by a failed attempt to update the device OS.
In short, i was unable to update my device to the last OS version. This blocked appx installations and also VS deploys.
For reference
http://www.ibtimes.co.uk/lumia-denim-update-installation-error-8018830f-developer-preview-devices-how-resolve-1482757
The only soultion I've found is to reset the device via the recovery tool mentioned in the above link
good luck
I am using Xcode version 5.0 and trying to use instruments,when i am running the script which contains "var target = UIATarget.localTarget();"
the following error appears :" Could not start script, target application is not frontmost."
It's known issue:
The message “Could Not Start Script : Target app is not frontmost” may be displayed when attempting to capture a UI Automation script in Instruments against the iOS 7 Simulator.
If this occurs, close the trace document and create a new one. 15387075
Source: Xcode 5.0.2 Release notes
i've followed this in order to flashbuilder 4.6 to use air sdk 3.4. no problems, or hiccups with the update.
the only problem is when i try to debug a mobile project using this sdk, either for android or ios i get the following error:
Process terminated without establishing connection to debugger.
invalid application descriptor: Unknown namespace:
http://ns.adobe.com/air/application/3.4
Launch command details: "C:\Program Files (x86)\Adobe\Adobe Flash
Builder 4.6\sdks\4.6.1\bin\adl.exe" -runtime "C:\Program Files
(x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.1\runtimes\air\win"
-profile mobileDevice -screensize 640x920:640x960 -XscreenDPI 326 -XversionPlatform IOS "C:\Users\joao\Adobe Flash Builder 4.6\teste34\bin-debug\teste34-app.xml" "C:\Users\joao\Adobe Flash Builder 4.6\teste34\bin-debug"
i've also got this problem.
following is what i've done:
1:create a new empty mobile application and debug it runs
2:open the new app's '{appname}-app.xml' file , find the 'xmlns' property in application root node for example
<application xmlns="http://ns.adobe.com/air/application/3.1">
3:replace the row of your old application
So i think the problem is your air sdk can not support the 3.4 version