Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[passkit] Update to beta 5 #2475

Closed
wants to merge 7 commits into from
Closed

Conversation

spouliot
Copy link
Contributor

No description provided.

@@ -761,7 +762,6 @@
</ItemGroup>
<ItemGroup>
<EmbeddedResource Include="Security\openssl_crt.der">
<LogicalName>monotouchtest.Security.openssl_crt.der</LogicalName>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please don't 😄

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder why the IDE removed it, seems to happen for other PRs too

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep I got that too...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@VincentDondain can you file a bug at the appropriate VSfM component ? thanks 😃

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@spouliot I would love to but I can't repro anymore. Might have an updated VS that fixed it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the IDE is technically right (it's removing the value because it's identical to the default value), but xharness currently needs the value when creating test variations (watchOS/tvOS projects).

@@ -27,7 +27,7 @@
<MtouchDebug>True</MtouchDebug>
<MtouchExtraArgs>-v -v -v -v</MtouchExtraArgs>
<AllowUnsafeBlocks>True</AllowUnsafeBlocks>
<MtouchArch>i386, x86_64</MtouchArch>
<MtouchArch>x86_64</MtouchArch>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this intentional?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think so

@monojenkins
Copy link
Collaborator

Build failure

[iOS (11,0)]
[Export ("paymentAuthorizationViewController:didAuthorizePayment:handler:")]
[EventArgs ("PKPaymentAuthorizationResult")]
void DidAuthorizePayment2 (PKPaymentAuthorizationViewController controller, PKPayment payment, Action<PKPaymentAuthorizationResult> completion);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Raaaaaah DidAuthorizePayment2... (:

I think you should XAMCORE-ify the name though (and the the other method).

Copy link
Contributor Author

@spouliot spouliot Aug 10, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's because of the events we added (we can't overload them) for that delegate
and XAMCORE might not help unless it's done when our minimum support is iOS11
it's not cute, but not unheard in .net, e.g. X509Certificate2 and it's friends :(

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and XAMCORE might not help unless it's done when our minimum support is iOS11

min support of iOS 11 or iOS 12?

Also I just don't understand what you mean here. If we decide to break the APIs again, like we did for classic / unified. Why does the minimum OS we support matters?

Copy link
Member

@rolfbjarne rolfbjarne Aug 11, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not the same selector with a new managed signature, it's the same managed signature used by two different selectors (i.e. both methods need to exist).

Copy link
Contributor

@VincentDondain VincentDondain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@spouliot
Copy link
Contributor Author

tests failed because I inverted an #if condition locally (to edit it outside of a project)

@spouliot spouliot added the do-not-merge Do not merge this pull request label Aug 10, 2017
@spouliot spouliot removed the do-not-merge Do not merge this pull request label Aug 11, 2017
@monojenkins
Copy link
Collaborator

Build failure

1 similar comment
@monojenkins
Copy link
Collaborator

Build failure

@monojenkins
Copy link
Collaborator

Build failure

1 similar comment
@monojenkins
Copy link
Collaborator

Build failure

@spouliot
Copy link
Contributor Author

hudson.plugins.git.GitException: Failed to fetch from https://github.com/xamarin/xamarin-macios

jenkins failed to pull :(

@spouliot
Copy link
Contributor Author

build

@monojenkins
Copy link
Collaborator

Build failure

2 similar comments
@monojenkins
Copy link
Collaborator

Build failure

@monojenkins
Copy link
Collaborator

Build failure

@monojenkins
Copy link
Collaborator

Build failure

@monojenkins
Copy link
Collaborator

Build failure

@spouliot
Copy link
Contributor Author

build

@monojenkins
Copy link
Collaborator

Build failure

@spouliot
Copy link
Contributor Author

issues with building the PR, will re-open the exact same one

@spouliot spouliot closed this Aug 11, 2017
@spouliot spouliot deleted the xcode9-passkit branch August 11, 2017 16:21
spouliot added a commit to spouliot/xamarin-macios that referenced this pull request Aug 11, 2017
Identical to PR2475 who suffered from a fatal git issue :(

[1] xamarin#2475
rolfbjarne added a commit to rolfbjarne/xamarin-macios that referenced this pull request Jul 26, 2021
New commits in xamarin/maccore:

* xamarin/maccore@7e6ffadb1f [Xamarin.Hosting] Only warn if we try to load a framework that doesn't exist. (xamarin#2473)
* xamarin/maccore@cc42300ec4 [Xamarin.Hosting] Xcode 13 b3 doesn't have IBFoundation anymore, but it does have AssetCatalogFoundation, which we must load. (xamarin#2474)
* xamarin/maccore@3e9801ee9a [Xamarin.Hosting] Improve error reporting when dlopen fails (xamarin#2475)

Diff: https://github.com/xamarin/maccore/compare/c67d7af80d005d8a1a4321e4e5d4d148918d960b..7e6ffadb1fe1a8e1444485a9915b04dcc07ab95b
rolfbjarne added a commit that referenced this pull request Jul 27, 2021
New commits in xamarin/maccore:

* xamarin/maccore@7e6ffadb1f [Xamarin.Hosting] Only warn if we try to load a framework that doesn't exist. (#2473)
* xamarin/maccore@cc42300ec4 [Xamarin.Hosting] Xcode 13 b3 doesn't have IBFoundation anymore, but it does have AssetCatalogFoundation, which we must load. (#2474)
* xamarin/maccore@3e9801ee9a [Xamarin.Hosting] Improve error reporting when dlopen fails (#2475)

Diff: https://github.com/xamarin/maccore/compare/c67d7af80d005d8a1a4321e4e5d4d148918d960b..7e6ffadb1fe1a8e1444485a9915b04dcc07ab95b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants