-
Notifications
You must be signed in to change notification settings - Fork 18
Packager giving ERROR on unrecognized feature id #128
Comments
Fixes blackberry#128 Reviewed By: James Keshavarzi <jkeshavarzi@rim.com> Tested By: Tracy Li <tli@rim.com>
It is fixed in the next release. ----- Original Message ----- This is currently blocking cordova support for bb10. Reply to this email directly or view it on GitHub: This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. |
eta? |
As per the milestone date, seems like 13 days. ----- Original Message ----- eta? Reply to this email directly or view it on GitHub: This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. |
Fixes blackberry#128 Reviewed By: James Keshavarzi <jkeshavarzi@rim.com> Tested By: Tracy Li <tli@rim.com>
When you have a config.xml file that has a feature id in it that is either not supported or not recognized it will give an ERROR.
The packager should be giving a WARNING. This is needed because developers use the same config.xml file for Smartphone, PlayBook and BB10. Since there are various levels of support, different functionality and ability for custom extensions we need to make sure we don't cause an error on packaging for BB10.
Throwing a WARNING should be the current observed behaviour on WebWorks for Smartphones and PlayBook.
The text was updated successfully, but these errors were encountered: