-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
ChromeOS #8
Comments
Given that Flutter doesn't directly target Chrome OS, I'm assuming you're referring to testing when Android app is built using Flutter and this plugin? If so, then no as I personally don't have a Chromebook. I'm not familiar with the level of support ChromeOS for Android apps (which is what it should come down as the plugin will use the Android APIs) but if you have a ChromeOS device then you could check to see how well the example app runs. |
Every flutter app i have tested runs on Chrome OS. I will try it out here... |
Yep I've read that Flutter apps will run like the Flutter gallery. I meant I don't know about the level of support ChromeOS has for the Android APIs |
AH you mean for the plugins ?
https://github.com/flutter/plugins
For example:
Sensors, Contacts, Camera, Battery etc ?
…On Thu, 19 Apr 2018 at 22:12 MaikuB ***@***.***> wrote:
Yep I've read that Flutter apps will run like the Flutter gallery. I meant
I don't know about the level of support ChromeOS has for the Android APIs
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATuCwhPtpaz0lYh1mjQS_ASMkAPUphSnks5tqO-5gaJpZM4TVFTF>
.
|
No this has nothing to do with Flutter. I meant if one were to write Android app with Java/Kotlin (as an example) and use the notifications API, then I don't know if those notifications would work on ChromeOS. If it does work then I would expect it to work to for this plugin as well since it uses the same APIs. If it doesn't then there's no much I can do. I suggest you read the following links in case you haven't done so https://flutter.io/platform-channels/ Plugins such as mine essentially just provided a bridge to use the platform's native APIs, so there's actually Android code (using Java or Kotlin) and iOS code (using Swift or Objective C) that has to be written. So when you use my plugin to show a notification, it will actually fire almost the same Java code you would've had to write if you had developed your app entirely in Java. Hopefully that's clarified what I'm referring to. On a different note, I've been cleaning up my plugin and will do another cleanup release soon. Unfortunately there are some breaking changes but they're more like fixing imports (that's already done in the latest release), renaming the plugin class and changing it so it will no longer be static. This is to facilitate mocking and testing when apps are using this plugin. Something I should've picked up on before so apologies for the inconvenience I'll be causing. I expect to be done with these changes and push out a new release within a day or the next few hours even |
Ok got it :)
I will setup my Chromebook for side loading and try out your flutter plugin.
Then we know for sure.
I am 99% sure it will work.
How about that ?
…On Fri, Apr 20, 2018, 12:34 PM MaikuB ***@***.***> wrote:
No this has nothing to do with Flutter. I meant if one were to write
Android app with Java/Kotlin (as an example) and use the notifications API,
then I don't know if those notifications would work on ChromeOS. If it does
work then I would expect it to work to for this plugin as well since it
uses the same APIs. I suggest you read the following links in case you
haven't done so
https://flutter.io/platform-channels/
https://flutter.io/developing-packages/
Plugins such as mine essentially just provided a bridge to use the
platform's native APIs, so there's actually Android code (using Java or
Kotlin) and iOS code (using Swift or Objective C) that has to be written.
So when you use my plugin to show a notification, it will actually fire
almost the same Java code you would've had to write if you had developed
your app entirely in Java. Hopefully that's clarified what I'm referring to.
On a different note, I've been cleaning up my plugin and will do another
cleanup release soon. Unfortunately there are some breaking changes but
they're more like fixing imports (that's already done in the latest
release), renaming the plugin class and changing it so it will no longer be
static. This is to facilitate mocking and testing. Something I should've
picked up on before so apologies for the inconvenience I'll be causing. I
expect to be done with these changes and push out a new release within a
day or the next few hours even
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATuCwvglLbXSIhe16MwNLe2OCoodszLBks5tqbm_gaJpZM4TVFTF>
.
|
Sounds good :) Just uploaded a new version btw so you should get the latest version |
a little snafu on mac build
|
ah bummer 2 options:
OR
|
so the good news is that cocoapods 1.4.0 no longer exists it seems. so looks like option 2 is the way to go. |
I'm only going to build against the latest "stable" (beta 2, 0.2.8) You tried switching channels as well? Sounds like it fixes one person there. Just concerned on if updating the template will break it for others |
Should add I know I'll likely have to fix this soon. Edit: sounds like the fix should be independent of whatever version of the Flutter SDK is installed, at least I hope so :) I'll give it a shot then |
Ok took a look but the issue being reported and fix just applies to iOS head projects associated with a Flutter app. It doesn't apply to iOS projects associated with Flutter plugin don't seem to be affected as they don't have a Podfile. I don't think there's nothing I need to change for plugin. In fact, my example project was still building after I updated. Perhaps your installation of the Flutter SDK from the master branch was before they pushed those new templates to master. If you were to update your installation and create a new app then I suspect the issue will be gone. Edit: looks like the example is not running on an older simulator so I'll have to fix that |
Back to your original issue though, did you have much luck with ChromeOS? |
Finally got a chance on Sunday night to try. Had to do my chores :) SO it works on ChromeOS nicely. If you want can hook it up and send whatever logs i get ? |
Sure you can but there's probably nothing I can do as I mentioned before. I'd suggest you try to create an Android app using only Java to see if you can reproduce the scenarios that aren't working in the example to see if it'll work. I'm pretty confident they won't as well on Chrome OS. Assuming this is the correct link, you can see that apps written directly for Chrome OS has fewer limited notification templates to select from https://developer.chrome.com/apps/notifications#type-TemplateType |
The link you gave is for the Chrome Browser... Its the same for ChromeOS. I really doubt it. Either way they are clearly eager to support it. I was looking on saucelabs for a ChromeOS hardware device to make it easier for you but they dont have them yet. Anyway i can run it here if need be.. |
Did you mean to say you doubt that it would work if you were do it entirely in Android? |
thats not what i am getting at. Basically it works on ChromeOS.. The last 3 dont, but the reason is because certain API's have not been ported to ChromeOS yet, but its clear that they will be. SO its better to just wait and get a Ci running against ChromeOS. Hence why i mentioned Saucelabs.. Saucelabs will be introducing Flutter and ChromeOS integration to the public. Its beta currently. Hope this helps. |
Got it though though in the end it would also mean it wouldn't have worked if it was written in Android as well :) I'm inclined to just close this as it's not an issue to do with the plugin or Flutter. Rather, it's a limitation of how well Chrome OS supports Android and it's APIs as per my initial reply |
cool ! closing and will see what happens on the ChromeOS side. |
Release/v1.0.4
Has anyone tested this on ChromeOS ?
The text was updated successfully, but these errors were encountered: