<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Warning: Don't use Android 4.x for Marketing Cloud Solutions in Adobe Experience Cloud Mobile Discussions</title>
    <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-mobile/warning-don-t-use-android-4-x-for-marketing-cloud-solutions/m-p/221930#M6</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Cory,&lt;/P&gt;&lt;P&gt;&amp;nbsp; Customer support is correct, it's no longer possible to set RSID or tracking server programmatically in any of the 4.x libraries. &amp;nbsp; We have moved to a configuration file to support a variety of upcoming enhancements (including post-release configuration changes, points of interest updates, and a few other tasty features we're not able to talk about yet). &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; I can totally understand how this can be frustrating initially -- especially if you're used to the previous way the libraries worked -- but we feel that programmatic configuration can lead to bigger issues with releases (and to poor development practices).&amp;nbsp; The ability to configure your app for different modes (test/dev/qe/release) is&amp;nbsp;better handled using one of the methodologies below:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Android -&amp;nbsp;&lt;/STRONG&gt;Use a build configuration tool like &lt;A href="http://maven.apache.org" target="_blank"&gt;Maven&lt;/A&gt;&amp;nbsp;or &lt;A href="http://www.gradle.org" target="_blank"&gt;Gradle&lt;/A&gt;&amp;nbsp;to inject the proper config file for the given build at compile time.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;iOS/OSX -&amp;nbsp;&lt;/STRONG&gt;Use a separate target for each build type, and only include the proper config file in each target.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;BlackBerry10 -&amp;nbsp;&lt;/STRONG&gt;Set your config file on a per-release-basis in the &lt;EM&gt;bar-descriptor.xml&lt;/EM&gt; file for your application.&lt;/P&gt;&lt;P&gt;&amp;nbsp; Similar methodologies can be used for other platforms (specifically WinRT/Windows Phone), and we'll provide documentation around those platforms when we provide the 4.x versions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Peter Fransen&lt;/P&gt;&lt;P&gt;Adobe Marketing Cloud - Mobile Engineering Team Lead&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 Oct 2015 02:26:02 GMT</pubDate>
    <dc:creator>meatcouch</dc:creator>
    <dc:date>2015-10-16T02:26:02Z</dc:date>
    <item>
      <title>Warning: Don't use Android 4.x for Marketing Cloud Solutions</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-mobile/warning-don-t-use-android-4-x-for-marketing-cloud-solutions/m-p/221929#M5</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In version 4 of the Android SDK they have stripped out the ability to programmatically point your code to a test RSID vs a production RSID. &amp;nbsp;This makes it very difficult to test your application without flooding your real analytics database with test data. &amp;nbsp;&lt;/P&gt;&lt;P&gt;When asking their customer support about this issue, they just confirmed to me that it is not possible for 4.x. &amp;nbsp;It really gives me "great confidence" that they are in touch with their customers' needs. &amp;nbsp;I guess the good news is that there is plenty of competition out there doing a much better job.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Oct 2015 02:26:02 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-mobile/warning-don-t-use-android-4-x-for-marketing-cloud-solutions/m-p/221929#M5</guid>
      <dc:creator>cory_smith1</dc:creator>
      <dc:date>2015-10-16T02:26:02Z</dc:date>
    </item>
    <item>
      <title>Re: Warning: Don't use Android 4.x for Marketing Cloud Solutions</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-mobile/warning-don-t-use-android-4-x-for-marketing-cloud-solutions/m-p/221930#M6</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Cory,&lt;/P&gt;&lt;P&gt;&amp;nbsp; Customer support is correct, it's no longer possible to set RSID or tracking server programmatically in any of the 4.x libraries. &amp;nbsp; We have moved to a configuration file to support a variety of upcoming enhancements (including post-release configuration changes, points of interest updates, and a few other tasty features we're not able to talk about yet). &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; I can totally understand how this can be frustrating initially -- especially if you're used to the previous way the libraries worked -- but we feel that programmatic configuration can lead to bigger issues with releases (and to poor development practices).&amp;nbsp; The ability to configure your app for different modes (test/dev/qe/release) is&amp;nbsp;better handled using one of the methodologies below:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Android -&amp;nbsp;&lt;/STRONG&gt;Use a build configuration tool like &lt;A href="http://maven.apache.org" target="_blank"&gt;Maven&lt;/A&gt;&amp;nbsp;or &lt;A href="http://www.gradle.org" target="_blank"&gt;Gradle&lt;/A&gt;&amp;nbsp;to inject the proper config file for the given build at compile time.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;iOS/OSX -&amp;nbsp;&lt;/STRONG&gt;Use a separate target for each build type, and only include the proper config file in each target.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;BlackBerry10 -&amp;nbsp;&lt;/STRONG&gt;Set your config file on a per-release-basis in the &lt;EM&gt;bar-descriptor.xml&lt;/EM&gt; file for your application.&lt;/P&gt;&lt;P&gt;&amp;nbsp; Similar methodologies can be used for other platforms (specifically WinRT/Windows Phone), and we'll provide documentation around those platforms when we provide the 4.x versions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Peter Fransen&lt;/P&gt;&lt;P&gt;Adobe Marketing Cloud - Mobile Engineering Team Lead&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Oct 2015 02:26:02 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-mobile/warning-don-t-use-android-4-x-for-marketing-cloud-solutions/m-p/221930#M6</guid>
      <dc:creator>meatcouch</dc:creator>
      <dc:date>2015-10-16T02:26:02Z</dc:date>
    </item>
  </channel>
</rss>

