[TIMOB-17830] Tizen folder with appicon.png included in ios IPA built for dist-appstore/dist-adhoc.
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | n/a |
Status | Open |
Resolution | Unresolved |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | Tooling |
Labels | cb-tooling |
Reporter | Stephen Feather |
Assignee | Chris Barber |
Created | 2014-10-08T10:51:58.000+0000 |
Updated | 2016-08-19T13:42:10.000+0000 |
Description
To reproduce, build a dist-appstore build from the cli, change the ipa name to zip, extract, peer inside.
!http://content.screencast.com/users/Stephen_Feather/folders/Jing/media/5d203be8-3c01-45ff-b21a-321928b7d0f2/00000610.png!
[~sfeather], which Titanium SDK is specified in the tiapp.xml?
3.4.0.GA
I am unable to reproduce the issue on: Mac OSX 10.9.5 Appcelerator Studio, build: 3.4.0.201409261245 Titanium SDK build: 3.4.0.GA Titanium CLI, build: 3.4.0 Alloy: 1.5.1 Xcode 6.0.1 I built both an Alloy and a Classic project for dist-appstore and dist-adhoc from the CLI, in the .ipa files neither had a 'tizen' folder, I then added
take a 3.3.x generated alloy project with tizen folders laying around (app/asset) comes to mind. Now we have to go clean up all the tizen crap littering our projects to that it doesn't make it into iOS (and i need to check android) binary packaging.
[~eharris] Try creating a project with 3.2.0.GA, then build the app for iOS and notice that the Tizen folder is NOT copied to the final build. Then update the
I am able to reproduce the issue on: Mac OSX 10.9.5 Appcelerator Studio, build: 3.4.0.201409261245 Titanium SDK build: 3.4.0.GA. 3.2.0.GA Titanium CLI, build: 3.4.0 Alloy: 1.5.1 Xcode 6.0.1 Revisited and using the information from the above comments I am able to reproduce the issue, if a project has existing Tizen resources then these are included when the app is built for dist-appstore or dist-adhoc. Thanks for the help.
This may seem like a non-issue being that Tizen is dead, but actually, this is a bug. We only identify folders in the
Resources
directory as platform folders if that platform exists in the current SDK. Instead, we should just create a list of all known platform names that have ever existing and combine it with the known platforms in an SDK (which will be mostly duplicates). We'll get this fixed in the next rev of the tooling.