Known Issues for OData SDK
Learn about known issues and apply workarounds for the OData SDK.
|
Issue #
|
Description
|
|
BCP #1580127839
|
Bitcode is not fully supported in Xcode 7
Workaround: Since Apple does not yet fully support bitcode, disable bitcode in project settings so that the SAP Mobile SDK version 2.3 SP07 application will build properly. |
|
BCP #1580127838
|
Android M environment setup
You must add a compile-time dependency if you target API level 23 or above. Workaround:
|
|
SMPONP-11143
|
The HTTP channel returns a 404 error when a request URL includes
".jsp".
The HTTP channel returns a 404 error when a request URL
includes ".jsp". For example, http://supServer:8000/ProxyEndpoint/backendFile.jsp?para1=val1¶2=val2 Workaround: In the <SMP_HOME>\deploy\webapps\httpchannel\WEB-INF\web.xml file, replace: <servlet-mapping> <servlet-name>JspServlet</servlet-name> <url-pattern>*.jsp</url-pattern> </servlet-mapping> with: <servlet-mapping> <servlet-name>DispatcherServlet</servlet-name> <url-pattern>*.jsp</url-pattern> </servlet-mapping> |
|
RTC-328
|
Relay Server: Server response containing
header with empty value is considered malformed.
When there is a PUT request passing through Relay Server to a SAP Mobile Platform proxy connection, you get an error message 400 - Bad request with no response from back end server. The root cause is whenever the GW server receives an HTTP request with an empty value in the header (for example, below HttpRespond contains the header key Vary and its values are empty), this issue occurs. Example ~~~~~~~~~~~~~~~~~~~~A sample respond message header~~~~~~~~~~~~~~~~~~~ HTTP/1.1 204 No Content Expires: Thu, 01 Jan 1970 00:00:00 GMT Set-Cookie: X-SUP-APPCID=283ec655-deaf-4ae6-8fe7-92dbbca4cf2f Date: Fri, 18 Jan 2013 01:49:19 GMT Vary: Content-Encoding: Cache-Control: no-cache, no-store, no-transform X-AUSERNAME: zxiong X-ASESSIONID: 1chn8gf Set-Cookie: atlassian.xsrf.token=BOC2-AB74-RK7A-C5C|b5297c7d951949fea3f91ccdd7025ff61c7e434c|lin; Path=/ X-Seraph-LoginReason: OK Set-Cookie: JSESSIONID=4A49B145411AE327021EE424EDB0B4F3; Path=/; HttpOnly X-AREQUESTID: 1069x403945x1.... Workaround: None. |
|
RTC-155
|
Push notification does not work with any security configuration other
than "admin" for certificate-based mutual SSL authentication.
If you use any other security configuration, you get an error message 403 - User not in required role. Workaround: Use single SSL with any security configuration or use "admin" as the security configuration for mutual SSL to enable Push notifications. |

