[Feature] Xamarin.iOS extension signing #30
Comments
|
@lassana thanks for opening this feature request as an issue in this repo. I know it would be great to see the same support for app extensions in Xamarin apps that we have for Obj-C/Swift apps. We'll keep this issue open to track total interest in having this supported. |
|
We also really need this. We have a Xamarin app with extensions |
|
I need this feature as well. App extensions are a core part of user experience nowadays. Would love to see this prioritized. |
|
Can we vote for this somewhere because we cannot build without. Extensions are used by most professional apps. |
|
We also seem to be hitting the same roadblock, we use an app extension for rich/enhanced notifications. I have also tried many things in Azure DevOps that all seem to fail as well. Is there anywhere we can vote for this in order to make it a higher priority backlog item? |
|
@JeroenBer @gzarkovic-livly please vote directly on this issue. This repository is helpful for our team to keep tabs on overall interest in feature requests. |
|
👍 My team uses xamarin iOS extensions and would like to see support for multiple provisioning profiles built into app center. |
|
Same here. We have two apps with extensions and would love to use app center build but cannot until this feature is available. |
|
This feature is also needed for our team. We're using iOS extension too. |
|
Hi guys. Is there any update? Because we needed it urgent :-/ Sorry but without it App Center doesn't work for us... |
|
@se No update to share at the moment. We've had our hands busy with other work this month and haven't been able to get to this. |
|
Please add |
|
Please add, or give us some workaround like from PreBuildScript |
|
I run a local jenkins server which gets a web hook from our git, builds the app, and then uploads it to AppCenter for distribution. AppCenter config screens are so much easier than having to deal with Jenkins. I'd really like to retire this build machine :P |
|
We had to configure our Xamarin iOS app targets to disable the extension project for testing in appCenter and we can't build there for production at the moment. Would love to have this added so we can stop depending on building locally and have the whole process automated. |
|
For everyone who needs this feature: iOS extension signing is possible in Azure DevOps: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/install-apple-provisioning-profile?view=azure-devops |
|
This is a blocker for us too. We really need support for Xamarin iOS extensions otherwise we need to move away from AppCenter and look at solutions like Bitrise or Azure DevOps |
|
i would appreciate this feature! |
|
Yeah we would like to see this feature coming to AppCenter. It has been a road block for us. |
|
I hate to be another "me too" guy - but yeah clearly App Center build is useless in this form for apps with a share extension. By the way, can the OP (@lassana) or anyone else rename this issue so the title says "extension" rather than "entension"? It'll make it easier to find (and upvote ;)) for other people. |
lassana
changed the title
|
Stuck in the same boat. Followed the OneSignal push notifications tutorial that appcenter shows as an option. The OneSignal tutorial walks through the iOS extension for notifications. Now my builds are broken because of this limitation. please fix this. Love AppCenter and how it makes things super easy. This would become very problematic. Is there any timeline yet on making this available? |
|
We're queuing the work now @skywalkerlol. Will take a bit to get done, but this will be active soon enough. |
|
We've completed support for this! Please try it out, and let us know if you have any feedback 😁 |
|
EDIT: Service is back up now. Original comment below,
I was super pumped to try this but AppCenter appears to be down :(
|
Awesome thanks for the update @nrajpurkar |
|
Did anyone try this? I get the same error as before... Like before the UI sees that I have a extension in my code. I upload the provision profile, appstore ready. The UI seems to forget the profile. I run the build. And I get the same error as before. Any thoughts? Regards |
|
@bo3po could you reach out to support via App Center portal? Would be great to collect more information and dig deeper into what you are seeing |
I have done so. When I get it working I will share it here. Might be something easy. But the error is the same that the build system is unable to find the provision profile even after I have uploaded it. The UI seems to forget the profile also. When I return to the build to see the configuration the profile is gone. No idea why. I can try with another browser. I use Chrome. |
|
Good news! In collaboration we have found the error. Seems to be related to Bitbucket repos. They will fix it soon and deploy the fix... That was fast! Love the support and effort they are putting into this... Keep it up! |
|
@bo3po thanks for reporting! We deployed a fix, and everything should work fine no. If anyone else experienced similar problems with configuring Bitbucket repositories, please try reconfiguring your branch (you might need to re-upload signing credentials) |
|
I had to adjust my pre-build script some 8 times, but I just managed to build successfully :D. |
|
@ElteHupkes that sound great. is the script something you could share perhaps? What did the trick? |
|
@bo3po These are mostly things very specific to my app (swapping out icons in Info.plist for production/beta builds and stuff). Something I can recommend paying attention to is whether you're building the solution or the project. We have a library with some unsafe code that wouldn't build when selecting the project in the configuration, because the project-level setting allowing unsafe code for the library wouldn't be picked up. When selecting the solution instead, the pre-build file needs to be in the same directory as the solution file, not the project file, that was messing with my brain a bit. I've had other problems in the past building at the project level, in particular with build configurations defined at the solution level. |
|
@ElteHupkes Ok. That is probably not relevent for my or other apps. I thought that you might have some provision magic in the file that would allow me to build with an ios extension project. Yes. Support was also asking where the plist was in releation to the csproj file. And that was ok. It was beside on the same folder level. |
|
It's working now thanks to the skilled team at microsoft that helped me diagnose the problem which was something wired with my build configuration on the server. I told the config not to sign. Save the config. And then re-added everything. That reset my config somehow and made it work. Great support. KEEP IT UP :) |
|
Hi guys, is it possible to add the same logic for building whole *.sln? |
|
Same for me. Solution doesn’t build. Fails on provisioning profile mismatch
…On Mon, Oct 7, 2019 at 6:06 PM Klim-Shoptagr ***@***.***> wrote:
Hi guys, is it possible to add the same logic for building whole *.sln?
Because when I tried to create build of whole solution with iOS project,
which contains extension, I faced with the same issue: I can't add more
than 1 Provision Profile...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#30?email_source=notifications&email_token=ABOM3H3BA5KK7T2Z7T4K6L3QNOXHNA5CNFSM4GULTT4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAR6OMI#issuecomment-539223857>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABOM3HYPSBF3EBYR5ORMZDTQNOXHNANCNFSM4GULTT4A>
.
|
|
@Klim-Shoptagr and @skywalkerlol Thanks for reaching out! We actually intentionally added support for building Xamarin.iOS projects with extensions from It'll be helpful to include the file structure of your repository (or if you're extra adventurous, a sample repository with the same structure as your project which reproduces the issue that you can share with us). Something like: We'll have some of this information from telemetry, but oftentimes it's useful to see our issues from the customer perspective as well :) Thanks! |
|
For what it's worth, I'm building from the solution level and for me it's working. |
|
This is what i have
.
+-- Foobar.sln
+-- Foobar
+-- Foobar.iOS
| Foobar.csproj
| Info.plist
+-- FoobarExtension
| FoobarExtension.csproj
| Info.plist
…On Tue, Oct 8, 2019 at 2:29 AM Elte Hupkes ***@***.***> wrote:
For what it's worth, I'm building from the solution level and for me it's
working.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#30?email_source=notifications&email_token=ABOM3H3YXDYVTTN2CKY7Y23QNQSDJA5CNFSM4GULTT4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAS7RNI#issuecomment-539359413>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABOM3H66UOHSVHC24JQWZNDQNQSDJANCNFSM4GULTT4A>
.
|
|
For those that are not having their extension detected, ensure that the reference in your container app csproj matches the extension's project Guid exactly. For example,
Mine was |
|
@dmariogatto For your GUID observations,
I'm double-checking, because if that's correct it sounds like a bug in App Center, notwithstanding you've identified a workaround. |
It seems that Visual Studio (Windows) uses the lower casing when creating an extension, while VS for Mac uses upper. |
|
@dmariogatto So is a "bug" opened on this either on appcenter or on visual studio ? |
|
@softlion Not that I know of... I did have a chat with AppCenter support, who said they were going to fix it in the near future. |
|
Any updates on this? Having same issue not showing extension project Provisional profile on iOS project in appcenter. |
|
It is fixed since a long time. AppCenter does not discover your extension. Look at appcenter doc on why it does not discover your extension and fix it. |
|
Its a xamarin.ios project it was showing couple of days ago but not now. |
|
@softsan It sounds like the original issues discussed in this thread, even if similar to what you're encountering, were confirmed addressed. So I'd recommend reaching out to the App Center Support channel directly. You can feel free to cite this issue to say "my symptoms look similar to this," though I recommend giving as much detail as reasonable as well as any relevant data to support it. That way the support team has the best chance of being able to accurately identify and help with your issue. You can find the support form in the App Center portal in the upper right hand corner ? > Contact Support |
|
@King-of-Spades Okay thanks. I've created a support ticket with AppCenter. |
and others
What App Center service does this feature apply to?
We would like to use VS AppCenter to build our Xamarin.iOS application for iOS devices (Ad-Hoc or AppStore builds, to be technical). Our application includes two iOS extension packages that require additional provisioning profiles to be present during the build process. Unfortunately, at the moment it is not possible: AppCenter allows me to upload only a single provisioning profile:
It was discussed a few times earlier:
Describe the solution you'd like
As a solution: adapt the same approach currently you use in native Obj-C/Swift builds: https://blogs.msdn.microsoft.com/vsappcenter/announcing-ios-app-extension-and-watchos-support-in-visual-studio-app-center/
Describe alternatives you've considered
As an alternative: do not limit clients with a single provisioning profile.
The text was updated successfully, but these errors were encountered: