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

App Build Failed on Xamarin Mobile Center with Telerik.UI.for.Xamarin

13 Answers 840 Views
Calendar & Scheduling
This is a migrated thread and some comments may be shown as answers.
Joel
Top achievements
Rank 1
Joel asked on 08 Mar 2017, 08:10 PM

I would like to say that recently we purchased Telerik.UI.for.Xamarin and added Telerik Nuget in our app. It works fine after integration and configured with our app. But App build fails on Xamarin Mobile Center (https://mobile.azure.com) with Telerik.UI.for.Xamarin. This happens when we try to create build.

Error: System.InvalidOperationException: Unable to find version '2017.1.10301.12' of package 'Telerik.UI.for.Xamarin'.

Full details are below:

System.InvalidOperationException: Unable to find version '2017.1.10301.12' of package 'Telerik.UI.for.Xamarin'.
2017-03-08T19:08:50.6756150Z   at NuGet.PackageHelper.ResolvePackage (NuGet.IPackageRepository repository, System.String packageId, NuGet.SemanticVersion version) [0x0006f] in <5168bb31f82348f797e7feef070997dc>:0 
2017-03-08T19:08:50.6770660Z   at NuGet.Commands.RestoreCommand.RestorePackage (NuGet.IFileSystem packagesFolderFileSystem, System.String packageId, NuGet.SemanticVersion version, System.Boolean packageRestoreConsent, System.Collections.Concurrent.ConcurrentQueue`1[T] satellitePackages) [0x000b2] in <572a211d3d4d428f91d5f3ddc03e5849>:0 
2017-03-08T19:08:50.6785020Z   at NuGet.Commands.RestoreCommand+<ExecuteInParallel>c__AnonStorey0+<ExecuteInParallel>c__AnonStorey1.<>m__0 () [0x0002c] in <572a211d3d4d428f91d5f3ddc03e5849>:0 
2017-03-08T19:08:50.6798310Z   at System.Threading.Tasks.Task`1[TResult].InnerInvoke () [0x00012] in <8f2c484307284b51944a1a13a14c0266>:0 
2017-03-08T19:08:50.6811850Z   at System.Threading.Tasks.Task.Execute () [0x00016] in <8f2c484307284b51944a1a13a14c0266>:0 
2017-03-08T19:08:50.6824940Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.6837750Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.6850480Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.6863490Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.6876180Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.6888880Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.6901680Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.6914440Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.6927490Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.6939880Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.6953100Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.6965990Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.6978710Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.6991540Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7004610Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7017310Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7030220Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7043160Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7055840Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7090570Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7103710Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7116690Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7129430Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7142260Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7154970Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7167920Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7180830Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7193640Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7206460Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7219190Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7232450Z namedmutex_create: error creating mutex handle
2017-03-08T19:08:50.7427260Z ##[section]Finishing: Restore Nuget

 

13 Answers, 1 is accepted

Sort by
0
Pavel R. Pavlov
Telerik team
answered on 10 Mar 2017, 07:34 AM
Hi Joel,

It seems that the build tries to restore our NuGet package but fails to do so. This behavior is expected because our NuGet package is hosted on a private server, it is not published in the official NuGet storage. We are using private server because only developers with licenses can use the Dev version of our controls.

To build your application you can either configure the build action to look for the NuGet package in our private server or you could use our binaries instead of our NuGet pack. 

Please give these suggestions a try and let us know how it goes on your side.

Regards,
Pavel R. Pavlov
Telerik by Progress
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
0
Brendan
Top achievements
Rank 1
answered on 18 Aug 2017, 12:43 AM

Hi Pavel,

I set up the nuget file to look at the Telerik server as shown below. However, the Mobile Center build is still failing. Same configuration and nuget.config file works and build the application in Team Services, but it does not in Mobile Center.

Here is the nuget.config:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageRestore>
    <add key="enabled" value="True" />
    <add key="automatic" value="True" />
  </packageRestore>
  <packageSources>
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
    <add key="telerik.com" value="https://nuget.telerik.com/nuget" />
  </packageSources>
  <disabledPackageSources />
  <activePackageSource>
    <add key="nuget.org" value="https://www.nuget.org/api/v2/" />
<add key="telerik.com" value="https://nuget.telerik.com/nuget" />
  </activePackageSource>
  <bindingRedirects>
    <add key="skip" value="False" />
  </bindingRedirects>
  <packageManagement>
    <add key="format" value="0" />
    <add key="disabled" value="False" />
  </packageManagement>
  <packageSourceCredentials>
    <telerik.com>
      <add key="Username" value="xxxxxxxxxxxxxxxx" />
      <add key="ClearTextPassword" value="xxxxxxxxxxxx" />
    </telerik.com>
  </packageSourceCredentials>
</configuration>

0
Stefan Nenchev
Telerik team
answered on 22 Aug 2017, 07:10 AM
Hello Brendan,

Unfortunately, we cannot be sure what is causing the issue based on only this information, however, it seems that it might be related to NuGet's mechanism of obtaining the packages. Did you have the chance to test if the build is successful when you manually add the references to your project? Would such approach work for you? 

Regards,
Stefan Nenchev
Progress Telerik
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
0
Richard
Top achievements
Rank 1
answered on 22 Jan 2018, 11:16 PM

Did this issue get resolved?

We build our mobile apps using app center and we were fixing to buy two licenses for your product, but if it doesn't work with CI/CD pipelines that's going to be a serious reason we can't use your product.

 

0
Yana
Telerik team
answered on 25 Jan 2018, 01:24 PM
Hello Richard,

Thank you for your interest in Telerik UI for Xamarin product.

As this is an older thread, we will have to check the updates in App Center in order to provide up-to-date information on how the Telerik assemblies could be referenced in a project built there. We will need some additional time to research what's the best approach you could take, I will write here as soon as we have a result ( in a day or two at latest).

In the meantime, you could download a trial version of the product and test whether it will be suitable for you, you can download it from here: Telerik UI for Xamarin Free Trial

Thank you for your patience.

Regards,
Yana
Progress Telerik
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
0
Yana
Telerik team
answered on 29 Jan 2018, 03:43 PM
Hello Richard,

We have tested building a Xamarin.Forms project with our Nuget packages referenced in AppCenter and I confirm the build was successful.  As explained earlier in this thread, you would need to provide the credentials to our private Nuget server (they are the same as in your Telerik account) inside a Nuget.config file ( you could check here for more details) - just make sure that you're using "ClearTextPassword" key for the password.

I hope this will be helpful. If you have any follow-up questions, let me know.

Regards,
Yana
Progress Telerik
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
0
Katarzyna
Top achievements
Rank 1
answered on 04 Apr 2019, 12:00 PM
HI All, 
 I have a similar issue on visual studio it works ok, on app I got  https://nuget.telerik.com/nuget/: Package 'Telerik.UI.for.Xamarin.2017.3.1214.2' is not found on source 'https://nuget.telerik.com/nuget/'. The credentials are ok, checked in visual studio. The config looks like that 
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>  
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
<add key="Telerik" value="https://nuget.telerik.com/nuget/" />
  </packageSources>
  <packageSourceCredentials>
    <Telerik>
        <add key="Username" value="mySampleUsr" />
        <add key="ClearTextPassword" value="MySamplePass" />
    </Telerik>
  </packageSourceCredentials>
  <packageRestore>
    <add key="enabled" value="True" />
    <add key="automatic" value="True" />
  </packageRestore>
  <bindingRedirects>
    <add key="skip" value="False" />
  </bindingRedirects>
</configuration>

0
Lance | Senior Manager Technical Support
Telerik team
answered on 04 Apr 2019, 02:15 PM
Hello Katarzyna,

There are three main reasons why a package search would not be successful:

1. That account doesn't have a license or account's license doesn't cover that version
2. The package version doesn't exist

Go to the UI for Xamarin downloads page and check that your account has access to that version:



If you do not see that version, you'll need to change your credentials to the account that did have that license or you contact Sales and ask they "backdate" your UI for Xamarin license.


Side note

You shouldn't be using clear text credentials in the nuget.config. You instead use the environment variable that AppCenter/DevOps provides. You can review the nuget.config I use in one of my demos: https://github.com/LanceMcCarthy/ComicVine 

Here's what the Environment variable section looks like in AppCenter:



Regards,
Lance | Technical Support Engineer, Principal
Progress Telerik
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
0
Katarzyna
Top achievements
Rank 1
answered on 04 Apr 2019, 09:40 PM
HI Lance, 
 thx for your help, problem sorted. Just updated the version of controls and everything goes as expected. 

Regards, 
0
Francis
Top achievements
Rank 1
answered on 24 Apr 2019, 05:41 PM

Hi,

I am having a similar issue with the Trial. AppCenter reports the following for all Telerik assemblies:

NU1102: Unable to find package Telerik.UI.for.Xamarin.Trial with version (>= 2019.1.318.1)

- Found 1 version(s) in nuget [ Nearest version: 2017.3.1030.1 ]

My account shows I have that version (see attached image). I only have one set of credentials, so that can't be an account mix-up.

 

0
Francis
Top achievements
Rank 1
answered on 24 Apr 2019, 06:15 PM

I updated the nuget.config and added the Env variables to App Center, and now I have the following error (it compiled fine before I installed Telerik). If I disable Multi-Dex, then I can't even compile locally. Min & target Android versions are 21 & 28.

 

What should I do to make a project with Telerik controls build on AppCenter? Is there a tutorial? (I could only find this post)

"/Users/vsts/agent/2.150.0/work/1/s/MyApp.Android/MyApp.Android.csproj" (PackageForAndroid target) (1) ->
(_CompileToDalvikWithDx target) ->
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(2721,3): error MSB6006: "java" exited with code 2. [/Users/vsts/agent/2.150.0/work/1/s/MyApp.Android/MyApp.Android.csproj]

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <add key="Local" value="ThirdParties" />
    <add key="nuget" value="https://api.nuget.org/v3/index.json" />
    <add key="Telerik" value="https://nuget.telerik.com/nuget" />
  </packageSources>
  <activePackageSource>
    <add key="All" value="(Aggregate source)" />
  </activePackageSource>
  <packageSourceCredentials>
    <Telerik>
      <add key="Username" value="%TELERIK_USERNAME%" />
      <add key="ClearTextPassword" value="%TELERIK_PASSWORD%" />
    </Telerik>
  </packageSourceCredentials>
</configuration>
0
Lance | Senior Manager Technical Support
Telerik team
answered on 25 Apr 2019, 03:08 PM

Hi Francis,

The nuget.config looks good. Additionally, your screenshot verifies your account let the Telerik NuGet server expose Telerik.UI.for.Xamarin.Trial v2019.1.318.

The first problem is likely due to trying to build too soon after starting a new trial. What likely happened is that you downloaded a new verison of the trial again, which adds the trial license to your account, however the Telerik NuGet server does not immediately reflect account changes. It usually takes 20-30 minutes for the change to propgate, but can sometimes take a few hours.

Regarding Exit Code 2, yes, that is usually due to needing Multidex after moving to API 28. The Android Support Libraries for v28.0.0.1 and later require Multidex because the references Android Support Libraries surpass the Davik Limit (See the official Android Developer Documentation).

What may be happening is that the project's Release configuration doesn't have Multidex enabled, try the following:

1. In Visual Studio, switch the build configuration to Release
2. Open the project Properties
3. Select the Android Options tab
4. Check the Enable Multi-dex
5. Set the Linking Behavior to SDK Assemblies only.

Here's a screenshot to guide you:



AppCenter Settings

Here's a screenshot of my App Center build setings (notice I have the latest SDK selected to build it with, sometimes this is too old)



Further Assistance

If you're still having issues building after applying these settings, please open a Support Ticket here so that the UI for Xamarin Android engineers can directly assist

Regards,

Lance | Technical Support Engineer, Principal
Progress Telerik
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
0
Francis
Top achievements
Rank 1
answered on 25 Apr 2019, 04:29 PM

This was a fantastic response to a rather vague question. The issue was I had set multidex on the Debug build but forgot to enable it in Release.

 

Outstanding service here--I am definitely buying your product. Thanks!

Tags
Calendar & Scheduling
Asked by
Joel
Top achievements
Rank 1
Answers by
Pavel R. Pavlov
Telerik team
Brendan
Top achievements
Rank 1
Stefan Nenchev
Telerik team
Richard
Top achievements
Rank 1
Yana
Telerik team
Katarzyna
Top achievements
Rank 1
Lance | Senior Manager Technical Support
Telerik team
Francis
Top achievements
Rank 1
Share this question
or