This is a migrated thread and some comments may be shown as answers.

Visual Studio Error after Update cannot start anymore

9 Answers 993 Views
AppBuilder extension for Visual Studio
This is a migrated thread and some comments may be shown as answers.
This question is locked. New answers and comments are not allowed.
Christopher
Top achievements
Rank 1
Christopher asked on 30 Nov 2015, 07:41 AM

So today I opened my Project in Visual Studio everything working fine, first thing I'm prompted that there is a telerik Update which of course I downloaded, a few minutes later I closed Visual Studio and wanted to open another Project when I get the following error "Der Objectverweis wurde nicht auf eine Objektinstanz festgelegt". Which is very dissapointing since I cant start Visual Studio anymore, since it worked fine before I did the Update, the Telerik Update killed something.

Hoping for a quick answer...

9 Answers, 1 is accepted

Sort by
0
Dimitrina
Telerik team
answered on 30 Nov 2015, 09:52 AM
Hello Christopher,

I am sorry to hear you experience such an issue. Currently, we are not aware of a problem and I could not reproduce the exception after updating the VS Extension installed on Visual Studio 2012,  Visual Studio 2013 and Visual Studio 2015. I updated through: AppBuilder -> Help -> Check for Updates -> Download -> Install.

Would you try the following:
- kill all left VS processes in the Task Manager and try starting it again.
- clear AppBuilder's Cache - you'll find it under the %localappdata%\Telerik\BlackDragon folder. Please remove the entire Cache folder.
- Clear Visual Studio cache for the installed extension - for VS 2013 you will find it under %localappdata%\Microsoft\VisualStudio\12.0\Extensions. 
reinstall the AppBuilder Visual Studio Extension.

In case there is still a problem, then may I request you to send us some additional information from:
- AppBuilder's logs - %localappdata%\Telerik\BlackDragon\Logs.
- the devenv logs (https://msdn.microsoft.com/en-us/library/ms241272.aspx)

Looking forward to hearing from you.

Regards,
Dimitrina
Telerik
 

Visit the Telerik Verified Plugins Marketplace and get the custom Cordova plugin you need, already tweaked to work seamlessly with AppBuilder.

 
0
Christopher
Top achievements
Rank 1
answered on 30 Nov 2015, 10:24 AM

Hey Dimitrina,

Thanks for your answer, I directly went for the Visual Studio Repair which took about 2 1/2 hours to complete but it seems that this fixed the Problem.

Regarding the logfiles there was not much to see there those were the last 2 Lines after logging in to Telerik Platform

[2015-11-30 07:58:37.676] Log (Info,Low): AppBuilder Update Available: 'An update is available. To be able to run any operations in the cloud, you need to update the extension to the latest version.
Do you want to download and install the update now? If you click No, you can go to the Visual Studio Gallery and manually apply the update later.' on 30.11.2015 07:58:37
[2015-11-30 08:31:54.222] Log (Info,Medium): AppBuilder for Visual Studio is shutting down...

0
Christopher
Top achievements
Rank 1
answered on 30 Nov 2015, 10:46 AM

Sadly it seems that something is still not right....,

I am able to open VisualStudio now, the Appbuilder Extension is up to date but when I try to deploy I get the following error:

 Fehler1Server build failed. Server output: Project "Datakey.tmp.proj" (default targets):
android Build Tooling revision 2015.11.25.2r
Warning: Note: Some input files use or override a deprecated API.
Warning: Note: Recompile with -Xlint:deprecation for details.
Warning: Note: /home/builder/BpcTooling/Cordova3/Plugins/com.telerik.LiveSync/src/android/LiveSync-Lib/LiveSync-Lib/src/com/telerik/LiveSync/CloudSync.java uses or overrides a deprecated API.
Warning: Note: Recompile with -Xlint:deprecation for details.
Warning: /tmp/builds/kf04PRIQCqlatXuUZ1/app/AndroidManifest.xml:26:5-43 Error:
Warning: uses-sdk:minSdkVersion 8 cannot be smaller than version 10 declared in library [app:CordovaLib:unspecified:debug] /tmp/builds/kf04PRIQCqlatXuUZ1/app/build/intermediates/exploded-aar/app/CordovaLib/unspecified/debug/AndroidManifest.xml
Suggestion: use tools:overrideLibrary="org.apache.cordova" to force usage
Warning: FAILURE:
Warning: Build failed with an exception.
Warning: * What went wrong:
Warning: Execution failed for task ':processArmv7DebugManifest'.
Warning: >
Warning: Manifest merger failed : uses-sdk:minSdkVersion 8 cannot be smaller than version 10 declared in library [app:CordovaLib:unspecified:debug] /tmp/builds/kf04PRIQCqlatXuUZ1/app/build/intermediates/exploded-aar/app/CordovaLib/unspecified/debug/AndroidManifest.xml
Warning: Suggestion: use tools:overrideLibrary="org.apache.cordova" to force usage
Warning: * Try:
Warning: Run with
Warning: --stacktrace option to get the stack trace. Run with
Warning: --info or --debug
Warning: option to get more log output.
Warning: /tmp/builds/kf04PRIQCqlatXuUZ1/app/cordova/node_modules/q/q.js:126
Warning: throw e;
Warning: ^
Error code 1 for command: /tmp/builds/kf04PRIQCqlatXuUZ1/app/gradlew with args: cdvBuildDebug,-b,/tmp/builds/kf04PRIQCqlatXuUZ1/app/build.gradle,-Dorg.gradle.daemon=true,-PcdvBuildArch=armv7,-PcdvBuildMultipleApks=true
Error: Build failed during execution
Error: 'Build failed with error code 8'
Done building project "Datakey.tmp.proj" -- FAILED.
.C:\Users\giustich\AppData\Local\Microsoft\VisualStudio\12.0\Extensions\0zlczig2.4ku\Targets\Build.targets1894Datakey

 I think it has something to do with the Cordova Version or the Manifest maybe the VS repair changed something there, but when I try to open the Project Properties I get another Error Message:

 Fehler beim Versuch der Methode "Microsoft.VisualStudio.Editors.ApplicationDesigner.ApplicationDesignerWindowPane.Initialize(), auf Methode "Microsoft.VisualStudio.Shell.WIndowPane.Initialize()" zuzugreifen.

 

 

0
Dimitrina
Telerik team
answered on 30 Nov 2015, 11:13 AM
Hello,

The reason for the build error seems to be that we have changed the build infrastructure on our servers to use Gradle for Android. We are sorry for this inconvenience. 

In order to resolve the problem you will have to use a newer version of the custom verified plugins in your project. Please go the the Package Manager dialog and update the plugins to the latest version. Also, if you are using other custom plugins in your Plugins directory make sure they are compatible. You can find a list of the issues we are aware of documented here: Breaking change introduces build failure for Android.

Let me know if this resolves the build error.

Regards,
Dimitrina
Telerik
 

Visit the Telerik Verified Plugins Marketplace and get the custom Cordova plugin you need, already tweaked to work seamlessly with AppBuilder.

 
0
Christopher
Top achievements
Rank 1
answered on 30 Nov 2015, 12:21 PM

Hello,

So since we were using the nfc plugin from the telerik-verified-plugins, I went there downloaded the latest version (18.Nov. 2015) Imported the plugin into VisualStudio and excluded the old Plugin from the Project and started to build. This is the only plugin included in the build Project I excluded the rest to prevent errors, but still I get the Error:

Ps: I then tried to exclude all Plugins and still get the same Error

Fehler42Server build failed. Server output: Project "Datakey.tmp.proj" (default targets):
android Build Tooling revision 2015.11.25.2r
Warning: Note: Some input files use or override a deprecated API.
Warning: Note: Recompile with -Xlint:deprecation for details.
Warning: Note: /home/builder/BpcTooling/Cordova3/Plugins/com.telerik.LiveSync/src/android/LiveSync-Lib/LiveSync-Lib/src/com/telerik/LiveSync/CloudSync.java uses or overrides a deprecated API.
Warning: Note: Recompile with -Xlint:deprecation for details.
Warning: /tmp/builds/nKFGfJXZ3snkB01ExA/app/AndroidManifest.xml:26:5-43 Error:
Warning: uses-sdk:minSdkVersion 8 cannot be smaller than version 10 declared in library [app:CordovaLib:unspecified:debug] /tmp/builds/nKFGfJXZ3snkB01ExA/app/build/intermediates/exploded-aar/app/CordovaLib/unspecified/debug/AndroidManifest.xml
Suggestion: use tools:overrideLibrary="org.apache.cordova" to force usage
Warning: FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':processArmv7DebugManifest'.
> Manifest merger failed : uses-sdk:minSdkVersion 8 cannot be smaller than version 10 declared in library [app:CordovaLib:unspecified:debug] /tmp/builds/nKFGfJXZ3snkB01ExA/app/build/intermediates/exploded-aar/app/CordovaLib/unspecified/debug/AndroidManifest.xml
  Suggestion: use tools:overrideLibrary="org.apache.cordova" to force usage
Warning: * Try:
Warning: Run with
Warning: --stacktrace
Warning: option to get the stack trace. Run with --info
Warning: or
Warning: --debug
Warning: option to get more log output.
Warning: /tmp/builds/nKFGfJXZ3snkB01ExA/app/cordova/node_modules/q/q.js:126
Warning: throw e;
                          ^
Error code 1 for command: /tmp/builds/nKFGfJXZ3snkB01ExA/app/gradlew with args: cdvBuildDebug,-b,/tmp/builds/nKFGfJXZ3snkB01ExA/app/build.gradle,-Dorg.gradle.daemon=true,-PcdvBuildArch=armv7,-PcdvBuildMultipleApks=true
Error: Build failed during execution
Error: 'Build failed with error code 8'
Done building project "Datakey.tmp.proj" -- FAILED.
.C:\Users\giustich\AppData\Local\Microsoft\VisualStudio\12.0\Extensions\0zlczig2.4ku\Targets\Build.targets1894Datakey

0
Michael
Top achievements
Rank 1
answered on 30 Nov 2015, 02:00 PM

Finally I found the Problem it seems that the min-sdk Version in my Android Manifest file was 8

<uses-sdk android:minSdkVersion="8" />

which I changed to 10 so now I am not getting this error anymore but now I am getting a (500) Internal Server Error

0
Tina Stancheva
Telerik team
answered on 30 Nov 2015, 05:08 PM
Hello guys,

With the AppBuilder 3.0 release, we introduced Gradle for Android builds, which provides stricter AndroidManifest validation as well as unified way to declare dependencies. This change, is now raising an error when there are conflicting minSDKVersions.

As the Cordova 3.7/8.x library for Android requires a minimum version of 10, if your project contains an AndroidManifest.xml file where the uses-sdk entry requires a minSdkVersion smaller that 10, an error will be raised.

As Michael suggested, in order to resolve the issue, please update the AndroidManifest.xml file in your project:

<uses-sdk android:minSdkVersion="10"/>
@Christopher - please let me know if that change resolves the issue on your side.

@Michael - can you please capture the HTTP requests AppBuilder performs on your side and submit them in a ticket. Please follow these steps:
  1. Download Fiddler from here and install it.
  2. Run Fiddler and go to Tools -> Fiddler Options.
  3. On the HTTPS page, verify that Capture HTTPS Connects is enabled.
  4. Verify that Decrypt HTTPS traffic is enabled with the ...from all processes option and minimize Fiddler to tray.
  5. Run Visual Studio and try to build your project
  6. In Fiddler, go to File -> Save -> All Sessions, save the archive to disk. This will produce a SAZ file.
  7. Zip the .saz file and attach it in a ticket

It would also help if you can attach your project and the AppBuilder logs (
%localappdata%\Telerik\BlackDragon\Logs) as well. In the meantime, please have a look at this forum post to see if the issue described there might be causing build errors on your side.

Regards,
Tina Stancheva
Telerik
 

Visit the Telerik Verified Plugins Marketplace and get the custom Cordova plugin you need, already tweaked to work seamlessly with AppBuilder.

 
0
Christopher
Top achievements
Rank 1
answered on 01 Dec 2015, 07:20 AM

Hello Tina,

Christopher & Michael here, changing the min Sdk Version to 10 worked, I can build and deploy without any errors,

I downloaded Fiddler and did as you described somehow when fiddler is running I cant build and Deploy getting this Error:

System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Die zugrunde liegende Verbindung wurde geschlossen: Für den geschützten SSL/TLS-Kanal konnte keine Vertrauensstellung hergestellt werden.. ---> System.Security.Authentication.AuthenticationException: Das Remotezertifikat ist laut Validierungsverfahren ungültig.

 

0
Tina Stancheva
Telerik team
answered on 02 Dec 2015, 02:00 PM
Hi guys,

I am happy to see the build now run successfully. I only needed the Fiddler to check the requests in case the Visual Studio build returns an Internal Server Error. In case, it no longer does, then you won't need to run it.

As for the error you're getting when initiating a build while Fiddler is running, I believe the cause to be  that your machine doesn't trust the Fiddler certificate. In case you need to use Fiddler in future to capture AppBuilder requests, please follow these next steps to ensure your machine trusts the Fiddler root certificate:
  • Run Fiddler and go to Tools -> Fiddler Options.
  • On the HTTPS page click on Export Root Certificate to Desktop
  • In Windows Explorer navigate to Desktop and double-click on FiddlerRoot.cer
  • Hit Install Certificate and install it for the Local Machine. Click Next.
  • Select Automatically select the certificate store based on the type of certificate. Click Next and then Finish.
  • Once you close the "The import was successful" alert, go back to Fiddler's Tools -> Fiddler Options->HTTPS
  • Verify that Capture HTTPS Connects is enabled.
  • Verify that Decrypt HTTPS traffic is enabled with the ...from all processes option and restart Fiddler.

Let me know if that helps.

Regards,
Tina Stancheva
Telerik
 

Visit the Telerik Verified Plugins Marketplace and get the custom Cordova plugin you need, already tweaked to work seamlessly with AppBuilder.

 
Tags
AppBuilder extension for Visual Studio
Asked by
Christopher
Top achievements
Rank 1
Answers by
Dimitrina
Telerik team
Christopher
Top achievements
Rank 1
Michael
Top achievements
Rank 1
Tina Stancheva
Telerik team
Share this question
or