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

4 posts, 0 answers
  1. Joel
    Joel avatar
    1 posts
    Member since:
    Jul 2010

    Posted 08 Mar Link to this post

    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

     

  2. Pavel R. Pavlov
    Admin
    Pavel R. Pavlov avatar
    1236 posts

    Posted 10 Mar Link to this post

    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
  3. Brendan
    Brendan avatar
    1 posts
    Member since:
    Jul 2016

    Posted 17 Aug in reply to Pavel R. Pavlov Link to this post

    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>

  4. Stefan Nenchev
    Admin
    Stefan Nenchev avatar
    503 posts

    Posted 22 Aug Link to this post

    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
Back to Top