[ALOY-1538] Alloy <FlexSpace> is wrapped with a deprecated API

GitHub Issue	n/a
Type	Bug
Priority	Critical
Status	Resolved
Resolution	Duplicate
Resolution Date	2017-01-27T10:55:12.000+0000
Affected Version/s	n/a
Fix Version/s	n/a
Components	XML
Labels	n/a
Reporter	Francisco Ruaro Varisco
Assignee	Hans Knöchel
Created	2016-08-31T02:08:09.000+0000
Updated	2017-01-27T14:46:47.000+0000

Description

Every time I use the Alloy FlexSpace component I get a warning. *Code:*

<TextField id="txtAmount" class="labelOrange label18Bold keyboardNumber">
            <KeyboardToolbar>
               <Toolbar>
                  <Items>
                     <FlexSpace />
                     <Button style="Ti.UI.iOS.SystemButtonStyle.DONE" onClick="onDoneClick">Done</Button>
                  </Items>
               </Toolbar>
            </KeyboardToolbar>
         </TextField>

*WARNING:* {noformat} [WARN] Ti.UI.iPhone.SystemButton.FLEXIBLE_SPACE DEPRECATED in 5.4.0, in favor of Ti.UI.iOS.SystemButton.FLEXIBLE_SPACE {noformat} You might have to change it to the new API's.

Comments

Sharif AbuDarda 2016-09-01 Hello, This is an warning. The app should build without any error. Thanks.
Francisco Ruaro Varisco 2016-09-01 It is building without any error, but it would be better not to have any warning as well. That's why I put the "type" of the ticket as "IMPROVEMENT" not "BUG" :)
Mostafizur Rahman 2016-09-04 Please update your project. That warning because, you are trying to use Deprecated functions. Thanks
Thomas Neerup 2016-11-01 So is deprecated? Please tell me what to use instead. dont seem to work anymore, tested on 5.5.1
Tim Poulsen (ACV) 2017-01-26 This should not be closed. This is an Alloy issue not a user project issue. I see the same WARN messages in my app using 6.0.1. Alloy is generating deprecated code when you use the tag. To Sharif -- you're right it's a warning not an error. But, Alloy should be updated to no longer generate the deprecated API call. To Mostafizur -- this code is being generated by Alloy. There's nothing users of your tool can do to have it generate the proper code. So, your comment is just meaningless.
Hans Knöchel 2017-01-27 This is a valid issue, caused by Alloy probably using the deprecated Ti.UI.iPhone namespace instead of Ti.UI.iOS. Although I think it's fixed for latest Alloy, I'll move to Alloy for further investigation next sprint.
Hans Knöchel 2017-01-27 Update: Checked this. [~nunocostapt] did an [Alloy PR](https://github.com/appcelerator/alloy/pull/798) last September to fix all deprecated API calls in Alloy. This should not occur in latest Alloy anymore and I cannot reproduce it. [~acvauctions], which Alloy /Ti version are you testing with? The patch was in Alloy 1.9.3 and SDK 6.0.0, see ALOY-1520.
Tim Poulsen (ACV) 2017-01-27 Below is what I'm running. I was seeing the WARN messages when generating a non-platform app and thus using 1.9.0. I see that my platform-generated apps are using the UI.iOS namespace properly. Sorry, I always forget that you guys embed separate versions within the appc/platform environment (a decision I didn't like back when I worked there and suggested then that it would cause confusion and issues). ≫ alloy -v 1.9.0 ≫ appc alloy -v 1.9.5

JSON Source