GithubHelp home page GithubHelp logo

nor0x / appcenter-xmac Goto Github PK

View Code? Open in Web Editor NEW
10.0 3.0 2.0 41.14 MB

AppCenter-XMac are Xamarin.Mac bindings for the AppCenter SDK

Home Page: https://johnnys.news/2022/01/AppCenter-XMac-is-dead-long-live-Microsoft-AppCenter

License: Other

C# 97.81% Shell 1.38% PowerShell 0.77% Batchfile 0.03%
appcenter xamarin-mac

appcenter-xmac's Introduction


๐Ÿ”ญ Iโ€™m currently working on: too many sideprojects @ github
๐ŸŒฑ Iโ€™m currently learning: fsharp
๐Ÿงช Iโ€™m experimenting with: Svelte + TypeScript
๐Ÿฅณ Iโ€™m hyped about: ML | dotnet | WASM
๐Ÿ’ฌ Ask me about: remote & nomadic work
๐Ÿ“ซ How to reach me: johnnys.page
๐Ÿ“ฐ Here is my blog: johnnys.news
๐ŸŽจ This is my portfolio: johnnys.page/portfolio
๐Ÿฑ Here is my bento: bento.me/johnny

๐Ÿ‘ค Pronouns: he / him
โšก๏ธ Fun fact: 95% of my sideprojects are stuck at the last 5%


MTFBWYA โœจ

appcenter-xmac's People

Contributors

achocron avatar cloudwu1 avatar dhei avatar dorothysun216 avatar dtrabo avatar elamalani avatar erychagov avatar evgeny-pol avatar guperrot avatar iamclement avatar jaeklim avatar jamminroot avatar luyaliu avatar matkovivan avatar mehrdadmzfr avatar micarls avatar nor0x avatar olmisa avatar owenniblock avatar owlstronaut avatar richa-d avatar snrnats avatar subhashvysyaraju avatar thyeggman avatar tjyung avatar udayanalla avatar v-eacaoi avatar vvechkanov avatar yuyaohu avatar zongrenfeng avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

Forkers

nickspag

appcenter-xmac's Issues

Crashes are not reported in AppCenter

First of all, signed builds are working with the 4.0.0 release, much thanks!!

Handled, but also unhandled exceptions are not visible in the Diagnose/Issues.
In the logflow are they visible only with an error_id.
Any idea?

Failure when nuget package is not added via PackageReference

First, great work @nor0x, and thanks for doing this! It's been a giant pain/gap in the Xamarin.Mac story.

Issue:

Using the library requires that your project has been migrated to restore packages via PackageReference nodes. When adding your package in the older Reference format it creates a bunch of messy hint paths, you see the bad-target AppCenter Assert in the console, and it generally doesn't work.

Unfortunately, VS4Mac's Xamarin.Mac templates still seem to use the older Reference style.

Suggestions:

I'm not familiar enough with msbuild to make any diagnoses on the actual problem, but I can follow this issue with a little PR making a note in the readme that should at least help people headoff any confusion. Most people are probably switching towards PackageReference by now anyway, so I'm not sure how large a barrier this is. But would help to clarify.

clang build errors

With both the 4.0.0 and 4.1.0 version, when I install either nor0x.AppCenter.Crashes or nor0x.AppCenter.Analytics (have not tried others) into the project I get 2 build errors.

  • clang : error : linker command failed with exit code 1 (use -v to see invocation)
  • MMP : error MM5309: Failed to execute the tool 'clang', it failed with an error code '1'. Please check the build log for details.

Looking into the build output...this is in part of the output:

  • MMP : warning MM2013: Failed to resolve the reference to \"Microsoft.AppCenter.MacOS.Bindings, Version=1.0.7676.24434, Culture=neutral, PublicKeyToken=null\", referenced in \"Microsoft.AppCenter.Crashes.MacOS.Bindings, Version=1.0.7676.24436, Culture=neutral, PublicKeyToken=null\". The app will not include the referenced assembly, and may fail at runtime.
    
  • MMP : warning MM2013: Failed to resolve the reference to \"Microsoft.AppCenter.MacOS.Bindings, Version=1.0.7676.24434, Culture=neutral, PublicKeyToken=null\", referenced in \"Microsoft.AppCenter.Crashes, Version=1.0.7676.24437, Culture=neutral, PublicKeyToken=null\". The app will not include the referenced assembly, and may fail at runtime.
    

I'm building with Visual Studio for Mac 8.8.4, Mono 6.12.0.113, Xamarin.Mac 7.0.0.15. On MacOS 10.15.7 and using XCode 12.2.

I've re-read the readme a few times. I don't know what else I might be missing. So am assuming some kind of bug? If I look in the nuget cache folder I see lib folders with dlls in it like "Microsoft.AppCenter.Analytics.MacOS.Bindings.dll". So I'm not sure if there is a disconnect in the name of the dll reference there somewhere.

App Store failed

I build my release with:

  • codesign --deep
  • <LinkMode>None</LinkMode>

Transporter worked well. But I got this email from App Store Connect:

Please correct the following issues, then upload again.

ITMS-90291: Malformed Framework - The framework bundle AppCenter (Cuterdio.app/Contents/Frameworks/AppCenter.framework) must contain a symbolic link 'AppCenter' -> 'Versions/Current/AppCenter'. Refer to the Anatomy of Framework Bundles for more information.

ITMS-90291: Malformed Framework - The framework bundle AppCenter (Cuterdio.app/Contents/Frameworks/AppCenter.framework) must contain a symbolic link 'Resources' -> 'Versions/Current/Resources'. Refer to the Anatomy of Framework Bundles for more information.

ITMS-90291: Malformed Framework - The framework bundle AppCenter (Cuterdio.app/Contents/Frameworks/AppCenter.framework) contains 'Headers', which should be a symbolic link -> 'Versions/Current/Headers'. Refer to the Anatomy of Framework Bundles for more information.

ITMS-90292: Malformed Framework - The framework bundle AppCenter (Cuterdio.app/Contents/Frameworks/AppCenter.framework) 'Versions' directory must contain a symbolic link 'Current' resolving to a specific version directory. Resolved link target: '${linkTarget}'. Refer to the Anatomy of Framework Bundles for more information.

ITMS-90291: Malformed Framework - The framework bundle AppCenterAnalytics (Cuterdio.app/Contents/Frameworks/AppCenterAnalytics.framework) must contain a symbolic link 'AppCenterAnalytics' -> 'Versions/Current/AppCenterAnalytics'. Refer to the Anatomy of Framework Bundles for more information.

ITMS-90291: Malformed Framework - The framework bundle AppCenterAnalytics (Cuterdio.app/Contents/Frameworks/AppCenterAnalytics.framework) must contain a symbolic link 'Resources' -> 'Versions/Current/Resources'. Refer to the Anatomy of Framework Bundles for more information.

ITMS-90291: Malformed Framework - The framework bundle AppCenterAnalytics (Cuterdio.app/Contents/Frameworks/AppCenterAnalytics.framework) contains 'Headers', which should be a symbolic link -> 'Versions/Current/Headers'. Refer to the Anatomy of Framework Bundles for more information.

ITMS-90292: Malformed Framework - The framework bundle AppCenterAnalytics (Cuterdio.app/Contents/Frameworks/AppCenterAnalytics.framework) 'Versions' directory must contain a symbolic link 'Current' resolving to a specific version directory. Resolved link target: '${linkTarget}'. Refer to the Anatomy of Framework Bundles for more information.

ITMS-90291: Malformed Framework - The framework bundle AppCenterCrashes (Cuterdio.app/Contents/Frameworks/AppCenterCrashes.framework) must contain a symbolic link 'AppCenterCrashes' -> 'Versions/Current/AppCenterCrashes'. Refer to the Anatomy of Framework Bundles for more information.

ITMS-90291: Malformed Framework - The framework bundle AppCenterCrashes (Cuterdio.app/Contents/Frameworks/AppCenterCrashes.framework) must contain a symbolic link 'Resources' -> 'Versions/Current/Resources'. Refer to the Anatomy of Framework Bundles for more information.

ITMS-90291: Malformed Framework - The framework bundle AppCenterCrashes (Cuterdio.app/Contents/Frameworks/AppCenterCrashes.framework) contains 'Headers', which should be a symbolic link -> 'Versions/Current/Headers'. Refer to the Anatomy of Framework Bundles for more information.

ITMS-90292: Malformed Framework - The framework bundle AppCenterCrashes (Cuterdio.app/Contents/Frameworks/AppCenterCrashes.framework) 'Versions' directory must contain a symbolic link 'Current' resolving to a specific version directory. Resolved link target: '${linkTarget}'. Refer to the Anatomy of Framework Bundles for more information.

Code object is not signed at all

As soon as I add the packages (without any additional code) my project that works well without it doesn't build anymore with those messages:

bin/Debug/myApp.app : error : /{myAppPath}: code object is not signed at all
bin/Debug/myApp.app : error : In subcomponent: /{myAppPath}/Contents/Frameworks/AppCenterAnalytics.framework

It is likely that this happens because my app is signed to work in sandbox and to be released on the App Store. Is there some way to fix this?

NuGet referencing error - Xamarin.Mac 7.8

it seems that upgrading Xamarin.Mac to version 7.8 (d16-9) causes some refercing errors in VS 4 Mac

image
I will make sure to have a custom assembly name for the macOS bindings in an upcoming PR

Compile error: The command exited with code 1

I have the linker disabled, I have migrated my packages.config to PackageReference and I am using the latest version of the nuget nor0x.AppCenter 4.4.0-XMAC, I have compiled, recompiled, cleaned the solution, deleted the bin and obj folder and restarted visual studio but the following error cannot be solved:

Compilation error The command "cd bin \ Debug \ myApp \ Contents \ Frameworks \ AppCenter.framework ; rm AppCenter; ln -s Versions \ A \ AppCenter AppCenter" exited with code 1.

Anyone have any idea what can happen? thanks for your attention.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.