[TIMOB-14642] Cloud: ti.cloudpush to use sender id according to acs app sender id settings
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2013-07-26T22:20:00.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | 2013 Sprint 15 API, 2013 Sprint 15, Release 3.1.2, Release 3.2.0 |
| Components | Cloud |
| Labels | n/a |
| Reporter | Ingo Muschenetz |
| Assignee | Paul Lv |
| Created | 2013-07-24T16:16:57.000+0000 |
| Updated | 2013-08-29T18:33:32.000+0000 |
Description
ti.cloudpush to use sender id according to acs app sender id settings(CLOUDSRV-2548)
PR: https://github.com/appcelerator/titanium_mobile_modules/pull/244 FR failed. Please see comment [here](https://github.com/appcelerator/titanium_mobile_modules/pull/244#issuecomment-21574364). The test app is attached in CLOUDSRV-2549.
SDK PR master: https://github.com/appcelerator/titanium_mobile/pull/4505 3_1_X: https://github.com/appcelerator/titanium_mobile/pull/4506
Tested this issue in below environment - Appcelerator Studio: 3.1.3.201308292449 Titanium SDK: 3.1.3.v20130828171413 ACS: 1.0.6 NPM: 1.3.2 Titanium: 3.1.2 ti.cloud: 2.3.7 ti.cloudpush: 2.3.2 Device - Nexus7 (v4.3) Result - Now we are able to receive push notification on device with sender id specified in the ACS website. Also the cloned issue CLOUDSRV-2549 is already marked as resolved and fixed. Leave this issue as it is because need to verify in 3.2.x SDK build.
Since Smitha has verified GCM push using sender ID with 3.1.2 GA and this ticket was also verified with 3.1.3 (which at submission to 3.1.2 was 3.2.0), this ticket has been verified in both branches and can be closed.