function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Deepu2123Deepu2123 

[sf:deploy] 560. applications/standard__Content.app -- Error: Property 'tab' not valid in version 43.0

Hi Developers,
I have a issue with [sf:deploy] 560. applications/standard__Content.app -- Error: Property 'tab' not valid in version 43.0

<?xml version="1.0" encoding="UTF-8"?>
<CustomTab xmlns="http://soap.sforce.com/2006/04/metadata">
<customObject>true</customObject>
<mobileReady>false</mobileReady>
<motif>Custom26: Flag</motif>
</CustomTab>

Please suggest me on this.
Raj VakatiRaj Vakati
Are you including profiles also as part of migation ?? If not include and try it will work .. 

Enable "Salesforce CRM Content" before deploying or Move Settings also along with it  .. Please refer this link 

https://help.salesforce.com/articleView?id=content_initialsetup.htm&type=5
  1.  From Setup, enter Salesforce CRM Content in the Quick Find box, select Salesforce CRM Content, and then select Enable Salesforce CRM Content.
  2. Give users access to Salesforce CRM Content by assigning feature licenses in one of the following ways:
  3. To assign feature licenses to users automatically, from Setup, enter Salesforce CRM Content in the Quick Findbox, select Salesforce CRM Content, and then select Autoassign feature licenses to existing and new users.
  4. To assign feature licenses to users manually, from Setup, enter Users in the Quick Find box, then select Usersand click Edit next to the user's name. Select the Salesforce CRM Content User checkbox and click Save.
Mohammad AnisMohammad Anis
Hi,

I had this same issue, looked around, and found the following in Summer '19 release notes:

Custom Tabs
REMOVED: The deprecated field mobileReady has been removed from the CustomTab object
The mobileReady field is left over from the deprecated Salesforce Classic Mobile app. This field indicated whether a Visualforce page appeared in the Salesforce Classic Mobile app.

https://releasenotes.docs.salesforce.com/en-us/summer19/release-notes/rn_api_meta.htm

So it appears the solution is to remove the deprecated fields from the your-tab-name.tab-meta.xml file.

Thanks