I m having 2 version of VS2017 and a mac with latest macOS.
I transfer my Xamarin forms App file from VS2017 enterprise to a machine(more than 3 years old but running win10 pro) with VS2017 Community version. When I debug ( with selecting Android project and VS-android-23 X86 tablet as emulator ) this App in VS2017 Community version , I have no compilation error but have these message:
Found conflicts between different versions of the same dependent assembly
that could not be resolved.
These reference conflicts are listed in the build log when log verbosity is set to detailed.
I could not understand this message. I have no problem running the same app in VS2017 Enterprize ver but I have this error message in VS2017 Community ver.
Update
Click View > Output --> this will show the error
1>Starting deploy VisualStudio_android-23_x86_tablet ...
1>Starting emulator VisualStudio_android-23_x86_tablet ...
1>C:\Users\xxxxx\AppData\Local\Android\ANDROI~1\tools\emulator.EXE -partition-size 512 -no-boot-anim -avd VisualStudio_android-23_x86_tablet -prop monodroid.avdname=VisualStudio_android-23_x86_tablet
1>emulator: ERROR: x86 emulation currently requires hardware acceleration!
1>Please ensure Intel HAXM is properly installed and usable.
1>CPU acceleration status: Please disable Hyper-V before using the Android Emulator. Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot.
1>Emulator VisualStudio_android-23_x86_tablet cannot be started.
Please help.
Related
I've got XCode 12.5 up and running on macOS 11.3 (M1 chip) in Github Actions as a self-hosted runner.
While my macOS workflow is able to find gl.h in the github-hosted machine just fine, my own self-hosted one reports this:
CMake Error at /Users/administrator/actions-runner/_work/Mudlet/Qt/5.14.2/clang_64/lib/cmake/Qt5Gui/Qt5GuiConfigExtras.cmake:9 (message):
Error: Failed to find "gl.h" in
"/System/Library/Frameworks/OpenGL.framework/Headers;/System/Library/Frameworks/AGL.framework/Headers".
Call Stack (most recent call first):
/Users/administrator/actions-runner/_work/Mudlet/Qt/5.14.2/clang_64/lib/cmake/Qt5Gui/Qt5GuiConfig.cmake:202 (include)
3rdparty/vcpkg/scripts/buildsystems/vcpkg.cmake:555 (_find_package)
/Users/administrator/actions-runner/_work/Mudlet/Qt/5.14.2/clang_64/lib/cmake/Qt5Widgets/Qt5WidgetsConfig.cmake:94 (find_package)
3rdparty/vcpkg/scripts/buildsystems/vcpkg.cmake:555 (_find_package)
/Users/administrator/actions-runner/_work/Mudlet/Qt/5.14.2/clang_64/lib/cmake/Qt5UiTools/Qt5UiToolsConfig.cmake:219 (find_package)
3rdparty/vcpkg/scripts/buildsystems/vcpkg.cmake:555 (_find_package)
3rdparty/edbee-lib/edbee-lib/CMakeLists.txt:177 (FIND_PACKAGE)
The code responsible is this line:
FIND_PACKAGE(Qt5UiTools REQUIRED)
What could be the reason that gl.h is not locatable?
I got this problem when I updated to MacOS Big Sur (11.6.2) when trying to make a qt app.
This was the error I got:
CMake Error at /usr/local/Qt-5.5.1/lib/cmake/Qt5Gui/Qt5GuiConfigExtras.cmake:9 (message):
Failed to find "gl.h" in
"/System/Library/Frameworks/OpenGL.framework/Headers;/System/Library/Frameworks/AGL.framework/Headers".
Call Stack (most recent call first):
/usr/local/Qt-5.5.1/lib/cmake/Qt5Gui/Qt5GuiConfig.cmake:139 (include)
My google-fu found this from 2019 [https://github.com/ziglang/zig/issues/2208]
https://github.com/ziglang/zig/issues/2208 :
The new path to the framework is:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks
I looked, and gl.h was found in several places, including OpenGL.framework.
As a work-around, I changed the library path in /usr/local/Qt-5.5.1/lib/cmake/Qt5Gui/Qt5GuiConfigExtras.cmake:9 from:
set(_GL_INCDIRS "/System/Library/Frameworks/OpenGL.framework/Headers" "/System/Library/Frameworks/AGL.framework/Headers")
to:
set(_GL_INCDIRS "/System/Library/Frameworks/OpenGL.framework/Headers" "/System/Library/Frameworks/AGL.framework/Headers" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks")
running on macOS 11.3 (M1 chip) in Github Actions as a self-hosted runner.
Try again with the latest version of self-hosted runners, since (Aug. 2022):
GitHub Actions: Self-hosted runners now support Apple M1 hardware
Actions runner support for Apple silicon hardware, such as the M1 chip, is now generally available.
This provides teams with the capability to run self-hosted macOS workflows in a macOS ARM64 runtime.
Now the Actions runner supports M1 and the ARM64 runtime meaning developers can run it on their own M1 or M2 hardware.
Based on initial testing, there are currently two issues to be aware of:
macOS ARM64 does not support node12.
Therefore, the runner will automatically use node16 to execute any javascript Action written for node12.
All actions provided by GitHub are compatible with the runner except for a known issue with setup-python. The fix for that can be tracked here.
For additional information on how to set up a self-hosted macOS ARM64 runner, please refer to our documentation.
If you have any feedback or questions for Actions self-hosted Apple silicon support, you can submit an issue in the runner repository.
When I try to open the Firebase assistent in Tools > Firebase an IDE Error occurs.
I've already tried to reinstall the Google Repository needed for this tool, reactivating the firebase plugins, and also reinstalled Android Studio (though without deleting all user settings).
Android Studio 3.1.3
Build #AI-173.4819257, built on June 4, 2018
JRE: 1.8.0_152-release-1024-b02 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
IDE Error:
Exeption in plugin Firebase Services. Moments ago. Occured 2 times since last clear. Undread. Disable Plugin.
null
java.util.NoSuchElementException
at com.google.common.collect.Iterators$1.next(Iterators.java:81)
at com.google.services.firebase.DependencyStateManager.getDependencyState(DependencyStateManager.java:60)
at com.google.services.firebase.DependencyStateManager.init(DependencyStateManager.java:109)
at com.android.tools.idea.assistant.view.StatefulButton.<init>(StatefulButton.java:122)
at com.android.tools.idea.assistant.view.TutorialStep.<init>(TutorialStep.java:106)
at com.android.tools.idea.assistant.view.TutorialCard.redraw(TutorialCard.java:153)
at com.android.tools.idea.assistant.view.TutorialCard.<init>(TutorialCard.java:90)
at com.android.tools.idea.assistant.view.FeaturesPanel.<init>(FeaturesPanel.java:84)
at com.android.tools.idea.assistant.AssistSidePanel.<init>(AssistSidePanel.java:81)
at com.android.tools.idea.assistant.AssistToolWindowFactory.createToolWindowContent(AssistToolWindowFactory.java:37)
at com.android.tools.idea.assistant.OpenAssistSidePanelAction.lambda$openWindow$0(OpenAssistSidePanelAction.java:59)
at com.intellij.openapi.application.TransactionGuardImpl$2.run(TransactionGuardImpl.java:315)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.runNextEvent(LaterInvocator.java:424)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.run(LaterInvocator.java:407)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:762)
at java.awt.EventQueue.access$500(EventQueue.java:98)
at java.awt.EventQueue$3.run(EventQueue.java:715)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:732)
at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:822)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:650)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:366)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
A quick search brought up the following procedure to fix the issue:
go to Settings > Plugins.
remove all Firebase plugins.
restart Android Studio.
back to Settings > Plugins.
enable the Firebase plugins again.
restart Android Studio.
Visual Studio Version:
14.0.25431.01 Update 3
Xamarin.Android Version:
7.0.2.42
Xamarin Forms Version:
Tried 2.3.3.193, 2.3.4.192-pre2 & 2.3.3.180.
Operating System & Version:
Win 10 Pro ver. 1607 build 14393.693
Google Play Services Version:
Xamarin.GooglePlayServices.Awareness ver. 42.1001.0
Describe your Issue:
Xamarin.GooglePlayServices.Awareness doesn't work with Xamarin Forms.
Error:
C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(2072,3): error MSB6006: "java.exe" exited with code 2
Steps to Reproduce:
Create a blank Xamarin Forms project & use Xamarin.GooglePlayServices.Awareness as described in Xamarin's blog post.
This error often caused by dex methods count limits. You should turn on "MultiDex" support in android project settings. Also you should update ProGuard in Android SDK (see Xamarin.Android release notes - https://developer.xamarin.com/releases/android/xamarin.android_7/xamarin.android_7.1/)
Recently installed VS 2015 Community Update 3 in Windows 10 Pro 32 bit. For the past couple days I have been playing with Cordova, but can not get it to work correctly.
I tried:
Redirect index.html hack.
Clearing cache in TACO settings
Repaired VS
This text is from the build log / VS / emulator / debug log / me.
Build: Warning: No emulator specified, defaulting to AVD_GalaxyNexus_ToolsForApacheCordova
Build: Failed to create Context 0x3005
VS: There were deployment errors. Continue?
Me: If I click Yes
Build: Debug is starting
Emulator: "The connection to the server was unsuccessful. (file:///android_assset/www/index.html)"
Me: App appears 3 times on emulator
Me: Breakpoints don't work. In the Debug log I see many messages "Cannot find or open the PDB file."
Me: Build log says the app was installed but Deploy failed?
Build:
Installing apk C:/Users/pears/Documents/Visual Studio 2015/Projects/BlankCordovaApp1/platforms/android/build/outputs/apk/android-debug.apk on emulator-5554...
INSTALL SUCCESS
Unlocking screen...
Running command "input keyevent 82" on emulator-5554...
Starting application "io.cordova.myapp6178b0/.MainActivity" on emulator-5554...
Running command "am start -W -a android.intent.action.MAIN -nio.cordova.myapp6178b0/.MainActivity" on emulator-5554...
LAUNCH SUCCESS
Executing "after_run" hook for all plugins.
Warning: No emulator specified, defaulting to AVD_GalaxyNexus_ToolsForApacheCordova
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
Me: I don't see any errors in the build log.
Update 7.22.2016
I created a new Azure VM (Windows 2012 R2 Datacenter, 64 bit, 2 core Intel 2.2, 7 GB RAM) and installed VS 2015 and Cordova. From the AVD manager, the base emulator started up fine. However, the deploy still failed for a blank Cordova project. I saw the white Cordova screen saying it was connecting to device. Then the same message "The connection to the server was unsuccessful. (file:///android_assset/www/index.html)". Maybe the Redirect index.html hack will help. I didn't try.
Next, I Installed the stand-alone Android Studio in my desktop Windows 10 VM for more options with the AVD and SDK. Immediately, it tells me my CPU doesn't support VT-x. Makes sense - it's an AMD processor. I started the AVD GalaxyNexus ToolsForApacheCordova emulator anyway and it never finished loading. It targets API 19, Android 4.4, and arm CPU. I tried upgrading to API 23 which refused to run and says:
Intel HAXM is required to run this AVD.
Your CPU does not support required features (VT-x or SVM).
Unfortunately, your computer does not support hardware accelerated virtualization.
Here are some of your options:
1) Use a physcal device for testing
2) Develop on a Windows/OSX computer with an Intel processor that supports VT-x and NX
3) Develop on a Linux computer that supports VT-x or SVM
4) Use an Android Virtual Device based on an ARM system image
(This is 10x slower than hardward accelerated virtualization)
It seems like VS failed to create an Android Virtual Device. You can create one in the version of Android Studio that VS installs on your machine. The default location is in "C:\Users[usename]\AppData\Local\Android\sdk\". Click on "Avd Manager" and create a device. Make sure its the only device created--any existing ones may be broken. Then, go back to VS and click "Android -> Build to Google Android emulator".
FYI--if you have Hyper V enabled (you are using a Windows Phone emulator), you should be selecting the ARM system image.
I'm using VS2015 Update 2 with TACO Update 9 and I'm attempting to debug an application on a iPhone 6S (iOS 9.3.1) attached to my Windows computer. The remote build is successful but I get the following messages when it attempts to debug the app:
2>------ Deploy started: Project: xyz, Configuration: Debug iOS ------
2>Found iTunes version: 12.3.0.44
2>Uninstalling app ID: com.bob.xyz.
2>Successfully installed .ipa file: D:\Documents\Projects\xyz\xyz\bin\iOS\Debug\xyz.ipa.
2>Starting idevicedebugserverproxy.exe at port 3000.
2>Cannot find the app installed on the device. Check that the device is connected, awake, and unlocked.
2>Deployment failed.
When I look on the device, I do not see the application. Are there steps I can take to further debug what might be causing the failure?
Make sure your solution is configured for Debug build and not Release.