why does it take so long ?

I'm trying to build an Android phone app that I've build before, now using Xamarin on VS 2019. Build becomes unbearably long. Here's an example I timed out using a stopwatch. Total time required to have the debug fail: Almost 30 minutes! Something is terribly wrong. Xamarin is no longer useable. Any suggestions (other than rehashing all those already posted) greatly appreciated. Thanks.

To Rebuild the code:
2:20 - build Release
5:40 - build Debug

To Debug:
4:00 - waiting for runtime check to complete
4:17 - remove old runtime
- installing shared runtime
- target device arm65-v8a
5:15 - installing the mono share rurntime (debug - ########)...
12:20 - Installing Platform Framework
13:00 - Installing the API 28 platform frame
13:40 - lot's of stuff
14:00 - detecting installed packages
14:30 - Copy application to device
16:45 - 100 % 2038k of 2038kb copied
25:35 - Getting installation path...
27:50 - Using fast dev path
28:00 - Couldn't connect debug

Tagged:

Answers

  • batmacibatmaci DEMember ✭✭✭✭✭
    You need to share your configuration. Probably you do some settings wrong
  • JarvanJarvan Member, Xamarin Team Xamurai
    edited August 12

    1.Try to delete the content files in bin and obj folder. Restart the vs and deploy app again.

    2.Or create a new project and move the code to the new project.

  • MichaelPliamMichaelPliam USMember ✭✭

    Not sure what you mean by 'configuration', but I think you mean the following:

    Microsoft Visual Studio Community 2019
    Version 16.2.1
    Microsoft.NET Frameworkd
    Version 4.7.03056

    Xamarin - 16.2.0.91
    Xamarin.Android SDK 9.4.1.0

    Dell XPS 8300
    Processor Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
    Installed RAM 8.00 GB

    System type 64-bit operating system, x64 based
    processor

    Windows 10 Pro
    Version 1803

    build is Lollipop (Android 5.1 - API 22)
    android_phone_armeabi-v7a(Android 5.1 - API 22)

  • MichaelPliamMichaelPliam USMember ✭✭

    The code builds in both debug and release configurations. The problem is invariable with the emulator.

    Typically, the output in debug mode reads:

    Starting emulator android_phone_armeabi-v7a ...
    1>Waiting for runtime checks to complete
    C:\Program Files (x86)\Android\android-sdk\emulator\emulator.EXE -no-boot-anim -avd android_phone_armeabi-v7a -prop monodroid.avdname=android_phone_armeabi-v7a
    emulator: WARNING: userdata partition is resized from 769 M to 800 MERROR: resizing partition e2fsck failed with exit code 8

    emulator: WARNING: encryption is off
    Warning: restoring GLES1 context from snapshot. App may need reloading.
    Emulator android_phone_armeabi-v7a is running.
    Waiting for emulator to be ready...
    WARNING: AsyncSocketServer.cpp:99: Error when accepting host connectionError message: Unknown error
    WARNING: AsyncSocketServer.cpp:99: Error when accepting host connectionError message: Unknown error
    WARNING: AsyncSocketServer.cpp:99: Error when accepting host connectionError message: Unknown error
    Detecting installed packages
    Detecting installed packages...
    Removing old runtime
    Removing old runtime: Mono.Android.DebugRuntime...
    Installing shared runtime
    Target device is armeabi-v7a.
    Installing the Mono shared runtime (debug - 1556497608)...
    1>Starting deployment to android_phone_armeabi-v7a ...
    1>Waiting for emulator to be ready...
    1>Emulator is not ready to be used.
    1>Deployment failed to android_phone_armeabi-v7a.
    ========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

    Device log output is voluminous but starts off:

    Unable to open connection to debuggerd:Connection refused
    Fatal signal 6(SIGABRT), code -6 in tid 4404(main)

  • MichaelPliamMichaelPliam USMember ✭✭

    I cannot get the emulator virtual device to work despite all my best efforts. I am about to abandon Xamarin and go back to Android Studio. That is, unless someone can help me to make sense of all this gibberish.

Sign In or Register to comment.