Does anyone know if this is for Remote deployments only? Or does it also affect Managed Cloud customers? Trying to find out if customers in the cloud need to be worried and addressing this proactively. Thanks,Gui
Thanks Roman! They do agree that this is likely a policy they have on Intune, but this is a large organisation and they will want us to make the App comply with the Intune SDK instead of changing it. I assume this will be a lot of work, would need R&D involved and might break all kinds of things. There is another option to explore which I haven't looked into: “wrapping tool" for Intune, but I am sure it also has a bunch of limitations and issues.
We tried to rename packages and it works, but is a nightmare. Hundreds of references in the source code to the original package name and some you have to leave as is and some you have to change to the new package name.I am trying this using build variants to create appended package names. It is working for prod so far, but the customer is not live and this hasn't been tested extensively. The new package name would look like: com.metrix.metrixmobile.<cust>prod.
Thanks Hans. I assume this would be available on u26 only (no downporting). Do you know if lots of code changes were needed and even new libraries required? That will give me a glimpse on how much work it might be needed for me to get the u22 customer working on a 33+ SDK.
I looked into the database and say that there is a message in the corresponding F1 table. That makes me think that the payload is present, but it is not showing on the screen. I will open a ticket with this being an issue.
The developer fixed this by decoding the file name and path fields in the attachment record itself, not early in the logic since the encoded name is needed for proper preview. This solution resolved new attachments, but the ones stuck can only be solved by initialising the device.Apparently this is fixed in FSM 6 u9, but I haven't tested myself.
Thanks Lee, that is a good document. Some further troubleshooting indicated this is a bug on FSM 6 u6 (possible all updates too) when one uploads a file that has spaces and other special characters such as [ and ] in its name. Those characters get encoded as %20, %5D, %5E in the file name in the mobile database and that is likely the cause.Even though the app is modified, I don't believe we modified this behaviour so it is likely a product bug. I will test it on R&D environment to be sure.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
