{ "id": "62551", "key": "TIMOB-1919", "fields": { "issuetype": { "id": "2", "description": "A new feature of the product, which has yet to be developed.", "name": "New Feature", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [], "resolution": { "id": "3", "description": "The problem is a duplicate of an existing issue.", "name": "Duplicate" }, "resolutiondate": "2013-03-14T18:49:20.000+0000", "created": "2011-04-15T03:05:36.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [], "versions": [], "issuelinks": [ { "id": "26718", "type": { "id": "10002", "name": "Duplicate", "inward": "is duplicated by", "outward": "duplicates" }, "outwardIssue": { "id": "104655", "key": "MOD-1013", "fields": { "summary": "Urban Airship Module for Google Cloud Messaging (GCM)", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "priority": { "name": "Critical", "id": "1" }, "issuetype": { "id": "7", "description": "gh.issue.story.desc", "name": "Story", "subtask": false } } } } ], "assignee": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2017-03-23T05:23:19.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10202", "name": "Android", "description": "Android Platform" } ], "description": "{html}
Right now Ti.Network.registerForPushNotifications only works\r\nwith iPhone.
\r\nAndroid 2.2 (Froyo) just added push notifications, called C2DM:\r\n\r\nhttp://android-developers.blogspot.com/2010/05/android-cloud-to-dev...
\r\nProblem is this only works with v2.2 devices and up.
Urban Airship has an approach that works with almost all android\r\ndevices...but I'm not sure how much you want to marry to them:
\r\n\r\nhttp://blog.urbanairship.com/blog/2010/09/08/push-notifications-on-...
In any case, some kind of built-in support for push on Android\r\nwould be great.
Don, I have an Android push module written and lightly tested\nand would be willing to give you guys the code if that'd help you\ncreate an officially-supported module quicker; let me know if\nyou're interested.
@Matthew I think there is going to be a module in the\nmarketplace for Urban Airship. We have enough features left for 1.5\nthat I don't think we're going to get any more modules done before\nQ1. Would you have any interest in adding yours to the market when\nit ships?
Possibly; we don't have resources to support it beyond our needs\nthough so someone else will likely need to take over support for\nit.
@matt, I'd be interested in taking over support for it if you\nguys will post it. Most of my upcoming projects require C2DM, and\ninstalling a 3rd party app like urban airship isnt kosher with my\nclients.
Would it be acceptable if I released the code under LGPL?
Please do! :)
\nMy application that I'd like to implement will involve a heavy\nuse of push notifications, so I could get a good amount of testing\ndone for anyone interested.
I'm really interested in this. Can you explain please how you're\ndoing a push in this instance, as the application would surely have\nto be inactive - so is the push a secondary application running in\nthe background, low memory footprint? Can you explain further\nplease. Is it true push?
Chris: I'm going to try to get the code out soon; sometime\nbetween tomorrow and the end of the month :p
\nPeter: True push: http://code.google.com/android/c2dm/index.html
Matthew, do you have twitter or somewhere I can follow the\nprogress?
How about GitHub? :)
\nhttps://github.com/IGx89/titanium-c2dm
\nI haven't done any development on it for a few weeks so it may\nbe broken with the latest 1.5.0 build, but changes should be minor.\nYou'll definitely want to update build.properties to the paths in\nyour local environment though. Feel free to change the package name\nfrom com.findlaw.titanium.c2dm to something else. Instructions on\nhow to build and test the module can be found here: http://developer.appcelerator.com/doc/mobile/android/module_sdk
Looks good! I'll see what I can do about implementing this\nsometime this week and give you some feedback. Thanks for your\ncontribution!
Looking forward to using C2DM in Titanium in current and future\napps.
\nAttempting to build this module. I've changed build.properties\nto reflect my environment. When I try to build with ant, or with\nEclipse, I get the following error:
\n/Library/Application\nSupport/Titanium/mobilesdk/osx/1.5.0/module/android/build.xml:10:\njava.lang.UnsupportedClassVersionError: Bad version number in\n.class file
\nMaybe something to do with Java version?
\n$ javac -version javac 1.6.0_22
\n$ java -version java version \"1.6.0_22\"
\nJava(TM) SE Runtime Environment (build 1.6.0_22-b04-307-9M3263)
\nJava HotSpot(TM) 64-Bit Server VM (build 17.1-b03-307, mixed\nmode)
Eclipse is set to use 1.5
\nLine 10 of that build.xml is:
\n\n<taskdef classname=\"org.appcelerator.titanium.ant.StringTask\" name=\"ti.string\" classpath=\"${ti.module.support.dir}/android/ant-tasks.jar\"/>
\n
\nDoes anyone have a pre-built zip of this module (if that would\nhelp), or any suggestions?
Just a follow up. I'm now able to build titanium-c2dm in Eclipse\nif I tell Eclipse to use Java 1.6