-
Notifications
You must be signed in to change notification settings - Fork 741
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
EarlGrey 2.0 | grey_allOf fails with "Doesn't support pointer returns" #1262
Comments
It seems to fail the same way in your swift test PS: I'm running Swift 5, XCode 11.4, iOS 13.4 |
Done some more digging. This may be a problem with The problem arrises in iOS 13.4. Swift 5 and Xcode 11.4 are not the culprits I believe as iOS 13.3 seems to work. The difference thats triggering the error is, for the method selector
in iOS 13.4, this triggers |
Hi John, Thanks for looking into this. As you have figured out, as of iOS 13.4, Swift array declares its I'm surprised of this change, as Swift array's I'm still looking at if there's any other side effects which are related to this. If you want to be unblocked right away, you can switch to NSArray when dealing with EarlGrey's API, such as grey_allOf. For example:
|
You can't really use Swift type as a remote object, because Swift does runtime checks in general. It shouldn't work and in Swift 5 it might have patched the hole to define Swift array more strict. The best way to fire a remote method is through @objc protocols, where Swift won't do the runtime check and goes thru the runtime dispatching machinery like what happens in ObjC. So what you can do, as mentioned by @AlbertWang0116 , is
|
Here's my workaround solution for the time being, once which I happen to like anyways...
|
Any possibility of merging this as a permanent solution? |
This is fixed by EarlGrey 2.2.1 release/eDO 1.0.2 release so you don't need the workaround. |
Calling
grey_allOf
with any arguments fails over the bridge.https://github.com/google/eDistantObject/blob/c6d5422f98ada571a8bad727cee67c6845d2f44c/Service/Sources/EDOInvocationMessage.m#L434
The text was updated successfully, but these errors were encountered: