<?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: Request errors in Mobile app in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Request-errors-in-Mobile-app/m-p/286868#M37673</link>
    <description>&lt;P&gt;There is no workaround for this with the classic DEM offering. Typically, I recommend using reporting errors from the mobile apps, as the web request errors in the mobile app might now have a direct impact on user experience (data can be cached). Relying just on HTTP codes for mobile apps might not provide the accurrate user experience.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Another solution can be to exclude the request completely. This can be accomplished on the app side, excluding the URL (iOS) or the class calling the URL (Android).&lt;/P&gt;</description>
    <pubDate>Thu, 25 Sep 2025 21:52:18 GMT</pubDate>
    <dc:creator>Julius_Loman</dc:creator>
    <dc:date>2025-09-25T21:52:18Z</dc:date>
    <item>
      <title>Request errors in Mobile app</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Request-errors-in-Mobile-app/m-p/286826#M37664</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I need to configure an exclusion for &lt;STRONG&gt;401 errors&lt;/STRONG&gt;, but only for a specific URL.&lt;/P&gt;
&lt;P&gt;From what I see, this is possible in the &lt;STRONG&gt;Web application&lt;/STRONG&gt; settings, but in the &lt;STRONG&gt;Mobile application&lt;/STRONG&gt; I only have the option to filter by error code, not by URL pattern.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;What is the reason for this limitation?&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Is there a possible workaround to achieve the same result?&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Regards, Deni&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Sep 2025 07:16:27 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Request-errors-in-Mobile-app/m-p/286826#M37664</guid>
      <dc:creator>deni</dc:creator>
      <dc:date>2025-09-26T07:16:27Z</dc:date>
    </item>
    <item>
      <title>Re: Request errors in Mobile app</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Request-errors-in-Mobile-app/m-p/286868#M37673</link>
      <description>&lt;P&gt;There is no workaround for this with the classic DEM offering. Typically, I recommend using reporting errors from the mobile apps, as the web request errors in the mobile app might now have a direct impact on user experience (data can be cached). Relying just on HTTP codes for mobile apps might not provide the accurrate user experience.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Another solution can be to exclude the request completely. This can be accomplished on the app side, excluding the URL (iOS) or the class calling the URL (Android).&lt;/P&gt;</description>
      <pubDate>Thu, 25 Sep 2025 21:52:18 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Request-errors-in-Mobile-app/m-p/286868#M37673</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2025-09-25T21:52:18Z</dc:date>
    </item>
  </channel>
</rss>

