-
Notifications
You must be signed in to change notification settings - Fork 67
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
Add support for iOS #15
Comments
Hi! when do you plan to work on this? |
Would love to see this! |
any plans? |
@ctacke : I would like to tackle the iOS port, unless you are close to a solution. Do you need help? Is there a prototype of sorts you would like to share? |
Nope, I've not even really started. Feel free to implement it and submit a pull request. The plan was to pretty much model the interface that Android has, so it shouldn't be too hard. |
No problem.
I will check in progress in a work branch as I go.
Cheers
…On Fri, Apr 13, 2018, 5:13 PM Chris Tacke ***@***.***> wrote:
Nope, I've not even really started. Feel free to implement it and submit a
pull request.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AD4qBCYTp3CwRoYE-C4cVK3CdiyMczYxks5toT8sgaJpZM4O6Qkq>
.
|
any progress on this? |
Yes!
I have been tending to the Android side of things since my client has been
eager to see a prototype on that platform, and first wanted a proof of
concept. Done.
This to say that I am now more than ever motivated to tend to the iOS side,
which is scheduled within the next 2 weeks.
Xavier
…On Mon, May 7, 2018 at 5:21 AM, PaulVrugt ***@***.***> wrote:
any progress on this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AD4qBOBArdXf5DIZlA3CgGBwZi-Vy64rks5twDxJgaJpZM4O6Qkq>
.
|
Any update on this? |
@SwiftArchitect I'm also curious about any progress |
Work in progress. iOS integration can be viewed here:
https://github.com/SwiftArchitect/universal-beacon/tree/issue%2315-Add-support-for-iOS
…On Wed, Jun 13, 2018 at 12:40 PM, PaulVrugt ***@***.***> wrote:
@SwiftArchitect <https://github.com/SwiftArchitect> I'm also curious
about any progress
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AD4qBIlZ-6rzFyVfUynM20meRn3Qdq6oks5t8WqggaJpZM4O6Qkq>
.
|
I tried to import the project running VS 15.7.4 on windows 10 and I can't make it work. I've got several error saying : UWP (uap10.0.10586) not compatible with .net standard 2.0. Do you have any idea how could I fix that ? |
Has Bringing UWP & Windows projects to @ctacke : who is handling the present PR#15 ? |
Has master or any other branch been maintained to catch up with up-to-date Xamarin.Forms? Yes the master branch from andijakl works fine. |
I'll check the latest status and merge / document everything in the following days! |
Fantastic
…On Wed, Jul 25, 2018 at 6:40 AM, Andreas Jakl ***@***.***> wrote:
I'll check the latest status and merge / document everything in the
following days!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AD4qBLb8Yyifw8xmsylQVAGUZSZhh-fFks5uKHVFgaJpZM4O6Qkq>
.
|
Hi, Very interested in a generic (provider's agnostic) component to iBeacons and EddyStones for all 3 Xamarin (UWP, Android & iOS). I integrated UWP & Android and build fine. Now I have to do some tests to received the packages, map to the frames and to look for updates. I really miss the iOS part. 80% devices are Androis, 17% iOS and the rest is other :-) Olivier |
I'm looking foward for the updates :) |
Still waiting for the PR approval I believe |
Checked the code today - generally looks excellent, great work! |
We have support for UWP and Xamarin.Android. We still need an iBluetoothPacketProvider implementation for iOS.
The text was updated successfully, but these errors were encountered: