If we try to catch the error and inspect the inner error. The inner exception complain about: This file can not be opened as a file descriptor; it is probably compressed.

Ask any AI, all will suggest adding AndroidAapt2NoCompress tag under property group in csproj.

<PropertyGroup>
 <AndroidAapt2NoCompress>tflite</AndroidAapt2NoCompress>
</PropertyGroup>

or with dot

<PropertyGroup>
 <AndroidAapt2NoCompress>.tflite</AndroidAapt2NoCompress>
</PropertyGroup> 

Unfortunately .NET compiler doesn’t seem to read this property. After more try and error, the solution is adding this instead.

<PropertyGroup>
 <AndroidAapt2LinkExtraArgs>$(AndroidAapt2LinkExtraArgs) -0 .tflite</AndroidAapt2LinkExtraArgs>
</PropertyGroup>

ERROR: The device must be paired before it can be connected. (com.apple.dt.CoreDeviceError error 2.)
The device must be paired before it can be connected. (com.apple.dt.RemotePairingError error 2.)

If you have the same problem, connect your iPhone to your Mac. Then open Xcode. Go to Window > Devices and Simulators. Select the iPhone that is currently connected and make sure it is trusted. If it is not, it will now force your iPhone to popup the trust this device dialog.

Previously if the device . iPhone isn’t trusted, it won’t even show up in the device list in Visual Studio for Mac. Now it will still show up but deploy always end in failure.

Source: https://developer.apple.com/documentation/xcode/running-your-app-in-simulator-or-on-a-device#Configure-the-list-of-simulated-devices

Let’s skip everything, I manage to patch the script to a temporary working condition. You can get it from https://github.com/ooikengsiang/MouseHunt-AutoBot/blob/master/MouseHunt-AutoBot.user.js but beware it is not in a good condition. I will continue to update the script later on.

Update: Version 2.08 available in the link above should address most of the issue caused by the new shiny horn.

I will not go very in depth on how Azure DevOps work. I also assume those who searching how to publish app to Huawei AppGallery via Azure pipeline should already experienced how to setup a release pipeline to publish to other store like Google Play Store. I also assume that you already publish the app to AppGallery before this.

Create API Client in AppGallery

1. Login to Huawei AppGallery Connect.
2. Go to Users and permissions.

3. Go to Connect API then click Create on the right.

4. In Create API client, give it a name (example: App Publish) and assign the Administrator role. DO NOT assign a project to this client. Leave the project as N/A else Azure pipeline will fail with 403 error. Click OK to create the API client.

5. Remember / noted the Client ID and Key. You will need them later.

Get App ID

1. In Huawei AppGallery Connect, go to My App.

Create A New Release Pipeline

1. Inside Azure DevOps, go to Release Pipelines.

2. Click on the New button and select New release pipeline to create a new release pipeline.

3. We will start with an Empty job without any template.

4. Since I already have a Android build pipeline setup and running already, I’m going to use the signed app (artifact) generated from that build pipeline as the source. This can be easily done by Add an artifact, then select the correct Project and Source (build pipeline). Important to remember the Source alias which we will need it later.

Add Tasks

Next, we already going to add task to the release pipeline. Go to Tasks.

Task 1: Install Python Request

1. Add a command line task.
2. Display name: Install Python request
3. Script:

cd C:\hostedtoolcache\windows\Python\3.8.1\x64\Scripts

pip install requests

Task 2: Get AppGallery Access Token

1. Add Python script task.
2. Display name: Get AppGallery access token
3. Script source: Inline
4. Script:

import requests

json_data = {"client_id":"$(client_id)","client_secret":"$(client_secret)","grant_type":"client_credentials"}

req = requests.post("https://connect-api.cloud.huawei.com/api/oauth2/v1/token",json=json_data)

res_data = req.json()

res_data = "Bearer " + res_data['access_token']

print("##vso[task.setvariable variable=access_token]"+res_data)

Task 3: Get Upload URL

1. Add Python script task.
2. Display name: Get upload URL
3. Script source: Inline
4. Script:

import requests

headers = {
    'Authorization': '$(access_token)',
    'client_id': '$(client_id)'
}

url = 'https://connect-api.cloud.huawei.com/api/publish/v2/upload-url'

data = {
    'appId':'$(appId)',
    'suffix':'aab'
}
response = requests.get(url,headers=headers,params=data)
res_data = response.json()
print("##vso[task.setvariable variable=authCode]"+res_data['authCode'])
print("##vso[task.setvariable variable=uploadUrl]"+res_data['uploadUrl'])

Task 4: Upload File

1. Add Python script task.
2. Display name: Upload file
3. Script source: Inline
4. Script (Important: Replace Source Alias with the source alias from release pipeline):

import requests

filePath = r'$(System.DefaultWorkingDirectory)\<Source Alias>\Build\drop\$(fileName)'

files = {'file':open(filePath,'rb')}

data = {'authCode':'$(authCode)','fileCount':1}

reponse = requests.post('$(uploadUrl)',data=data,files=files)

text = reponse.json()

file_info = text['result']['UploadFileRsp']['fileInfoList'][0]

file_size = str(file_info['size'])

print("##vso[task.setvariable variable=fileDestUrl]"+file_info['fileDestUlr'])

print("##vso[task.setvariable variable=size]"+file_size)

Task 5: Update App File Info

1. Add Python script task.
2. Display name: Update app file info
3. Script source: Inline
4. Script (Important: replace en-US to language-region of the main language supported by your app):

import requests

file_size = int($(size))

headers = {
    'Authorization': '$(access_token)',
    'client_id': '$(client_id)'
}

params = {
    'appId':'$(appId)'
}

data = {'lang':'en-US','fileType':5,'files':[{'fileName':'$(fileName)','fileDestUrl':'$(fileDestUrl)','size':file_size,'imageResolution':'','imageResolutionSingature':''}]}

reponse = requests.put('https://connect-api.cloud.huawei.com/api/publish/v2/app-file-info',headers=headers,json=data,params=params)

text = reponse.json()

Task 6: Submit

1. Add Python script task.
2. Display name: Submit
3. Script source: Inline
4. Script:

import requests

headers = {'Authorization': '$(access_token)','client_id': '$(client_id)'}

params = {'appId': '$(appId)'}

r11 = requests.post("https://connect-api.cloud.huawei.com/api/publish/v2/app-submit",params=params,headers=headers)

res_data = r11.json()
print(res_data)

You should have a total of 6 tasks in your release pipeline by now.

Add Variables

Next, we are going to add the variable with value taken from Huawei AppGallery in order to make the pipeline work.

• Add “appId” variable with App ID retrieved from Huawei AppGallery.
• Add “client_id” variable with Client Id from Huawei AppGallery.
• Add “client_secret” variable with Key from Huawei AppGallery.
• Add “fileName” variable with file name of signed app generated from release pipeline. (Refer to your previous build pipeline run if needed. Example com.app-Signed.aab)

Complete

Remember to click Save to save the whole setup. Click Create release to see if everything is setup correctly. If you have problem access to the API or there is any API change, you can refer to their AppGallery Connect API document.

For iOS simulator, first you need to install the older version of iOS simulator from Xcode.

1. Launch Xcode.
2. Open Preferences by go to top menu > Xcode > Preferences.
3. Open Components tab.
4. Select and install the iOS simulator version you prefer by clicking on the small download button on the left.
5. The download / installation might take some time.

Just install the older simulator is not enough, you need to manually create a simulator for this version too.

1. Still inside Xcode.
2. Open Devices and Simulators by go to the top menu > Window > Devices and Simulators.
3. Switch to Simulators tab.
4. Click the small + button on the bottom left.
5. Enter a name for the simulator (it even suggested a name for you).
6. Remember to select the correct iOS version you need.
7. Click OK and you should see the newly created simulator added to the list of simulator on the left.

Once you have installed and created the iOS simulator. Then only Visual Studio for Mac will be able to show the new simulator in the simulator list. You might need to restart Visual Studio for Mac for the simulator list to be refreshed if Visual Studio for Mac already running when you create the simulator.

One thing to keep in mind that older simulator doesn’t get removed automatically when you update your Xcode.

In 2018, I decided to quit my job at Intel to join a newly startup company, Boostorder (parent company: Instanture, sister company: Mango Fintech) believing their promise and future potential. Before that, I do all my homework before joining the startup. The company have received a new funding from a multinational company, financial check. One of my friends recommend the director as trustable, leadership check. I even visited the company myself to understand their work and product, all check. Obviously, they promised a lot, but do they actually deliver them is another story.

October 2019

After many empty promises and disappointments, I decided to resign and submitted my resign email on 10^th October. The director, Chuah Teong Kee and I have a small, heated exchange when he known that I had resigned. In the end, we verbally agreed that if the company still need my assistance on my final week in the company, I will continue to work at the office and company will cash out my remaining annual leave if it happens.

December 2019

After discussion with my direct manager, he determined that my assistance was not needed in the final week. So, I applied my annual leave on 1^st December as planned and did not went to the office from 2^nd to 6^th December. This is where the horror story start.

At the end of December, I found out that I did not receive my remaining salary and some of my parking expanses. I sent two reminder emails to the director on 24^th and 30^th December. No reply from both emails.

January 2020

On 7^th January, I sent a Whatsapp message to the director to remind him about the email and salary. Read but no reply.

On 13^th January, I message my direct manager and another director in the company and explain to them what had happened. My direct manager replied that he already informed the director, but no reason is given, and no action is taken. While the other director in the company, Khoo Ta Kang refuse to help me citing that he is powerless against another director and do not want to get involved in this.

On 17^th January, I went to office personally to seek a valid reason. The director refused to speak with me and told me that he will call police to get me arrested for trespassing private property if I did not leave the office immediately. I leave the office immediately.

February 2020

With advice from friend, I filed a small claim against the director of the company at Balik Pulau Court on 24^th February. I naively though the company will just pay me back after they got the court letter. I was dead wrong.

Side note: Why small claim? Because it does not require a lawyer representation. Why not seek help from Department of Labour of Peninsular Malaysia? I tried but they cannot help me due to some law that written in year 1955 and did not get updated ever since.

No reply from the company after they received the court document. On 28^th February, the director shows up with a lawyer in the court proceeding. Surprise! They claim that they refused to pay my salary because I did not apply my annual leave on time as written in the employee handbook: “All annual leave must be applied one week before”. I checked the employee handbook; this rule does not exist. They also claim that I did not submit my parking expanses, which I did, and I can easily prove them. Then I realized that this is not going to end without a fight, and they are not going to play fairly.

Side note: The small claim should be file against the company instead of the director because it is company that own my salary, not the director personally. This is corrected by the judge on the proceeding.

March 2020 – February 2021

MCO 1.0 and 2.0 hit. Court close and case get delayed multiple times. Still, I must go to court personally multiple times, sit in the court room waiting to get a new date and time for each time the case gets delayed. Unlike the lawyer, I do not get pay for this.

April 2021

Court hearing finally happen on 22^nd April. Unsurprisingly, the director and lawyer show up in court hearing with a “updated”employee handbook which contain the new rule: “All annual leave must be applied one week before”. Surprise, surprise. Luckily, I have the old employee handbook and debunked their claim. I also have all my parking expanses digital report to backup. Their defends is down from “This employee break our company’s rule when he applied annual leave less than 1 week as required” to “The 1-week rule is not really relevant, it is unreasonable to approve leave on Sunday because it is hard to find a replacement”. Nice U-turn, Mr. Lawyer. I never know software engineer / developer need a replacement when they are on leave. Also, startup company don’t work on Sunday you say?

I also pointed that if the company honestly think that I broke the company’s rule or policy and refused to pay my remaining salary, they have plenty of opportunity to tell me when I email or message them to remind them about the salary. Instead, they refused to speak with me or reply any of my email and message and even threaten me to get me arrest when I meet them in person. This is simply just a retaliation against me for leaving the company.

Side note: If anyone who know about civil court’s process, all party must perform document filing and exchange document between parties before court hearing. I did my document filing and waited for them to exchange document with me. Technically I should know if they have submitted the “updated” employee handbook as evidence before the court hearing, but their lawyer told the judge that he does not know the process thus did not do the document filing before court hearing.

I going to skip the rest of the court hearing details because a programmer arguing with a lawyer in court is not as interesting as you can imagine.

May 2021

On 6^th May, the court finally ruled that the company must pay back my remaining salary. Before I manage to get the court ruling document done, MCO 3.0 hit follow by FMCO. Although the court still open during this time, to avoid unnecessary trouble and reduce non-essential travel, I opt to wait until the MCO lifted.

On 10^th May, I received a mail from defendant’s lawyer informing me that Boostorder has already made the payment as order by the court on 7^th May, which the company own me a year and half ago. Thank you very much?

October 2021

FMCO become Recovery Plan and it never end. Finally I get my 2 shot of vaccinations, and able to safety travel a cross district to the court in order to get the final court ruling document done. Delivered a copy to Boostorder. Although they have paid me in May, I still want to get all the paperwork done (better safe than sorry especially dealing with a shady company and a dishonest employer).

Conclusion

So, let me recap. I spend more almost 2 years fighting in court to get back the salary I lawfully earned at the first place. To be honest, the cost for all court filing and annual leave applied to attend the court in person, it already far excesses the remaining salary I tried to claim back. Not to mention the risk of catching Covid-19 whenever I attend the court.

Did the company get punished for not paying their employee as required by the law? No.

Did the company get punished for owning employee’s salary for more than a year? No.

Did the company get punished for submitted a forged evidence in court? No.

I’m just lucky to win in this court case. There are so many ways this court case can fall apart. What if my ex-employer claim that I did not submit my annual leave application at all? The HR system is under their control and who will think of taking a screenshot when apply for annual leave? What if I go to court without my old employee handbook with me? If I did not win the court case, every time other companies perform a background check on me when I apply a new job, do you think Boostorder will say nice word about me? My employment record and court record will be toasted!

What have I learned? In Malaysia, company can easily get away from not paying their employee if they are willing to pay the lawyer. Not many employees are willing to go through the legal trouble. For foreigner, that is even harder. Even if they do, what is the worst thing that can happen to the company? Pay back the salary and they are off to go. If employee decided to take their frustrations to the social media instead, it does not make any difference, employee still is not getting back their salary and a defamation lawyer letter maybe waiting in their inbox. So, if any of you happened to face the same situation as mine where ex-employer own your remaining salary. My advice for you “Forget about it”. If you insist on talking the same path as mine, my advice will be “Good Luck” because you really need all the luck to win.

Startup in Malaysia. Don’t get me wrong, this is not a story about me bashing how bad startup culture are in Malaysia. There are many good startup companies out there in Malaysia and even in Penang. But Boostorder / Instanture is not one of them and their bad behavior deserved to be call out because it is very damaging to local startup. Imagine if anyone who joined this startup company and went through such bad experience, will he / she choose another startup company again in the next job? Even worse, if an intern who joined such startup company during internship, will he / she spread good word about startup when he / she returns to the university / college?

Bonus: A lot of you asked me what have I done to the company caused that the director to go after me? I HAVE NO IDEA! I am working my ass off even on the last day in the office, porting Xamarin library, helping others to hunt bug in the app. Even after I left the company, I never turn down other ex-colleague request for help when they messaged me. The only thing I did was, I resigned from my position and like most employees who left this company, it is not a happy ending.

if (UIDevice.CurrentDevice.CheckSystemVersion(15, 0))
{
    // change the background and text color of title bar
    var appearance = new UINavigationBarAppearance();
    appearance.ConfigureWithOpaqueBackground();
    appearance.BackgroundColor = CustomColor.AccentColor;
    appearance.TitleTextAttributes = new UIStringAttributes() { ForegroundColor = CustomColor.ForegroundColor };
    appearance.LargeTitleTextAttributes = new UIStringAttributes() { ForegroundColor = CustomColor.ForegroundColor };

    UINavigationBar.Appearance.StandardAppearance = appearance;
    UINavigationBar.Appearance.ScrollEdgeAppearance = appearance;
}
else
{
    // change the background color of title bar
    UINavigationBar.Appearance.BarTintColor = CustomColor.AccentColor;
    UINavigationBar.Appearance.Translucent = false;

    // change the title text color
    UINavigationBar.Appearance.TitleTextAttributes = new UIStringAttributes() { ForegroundColor = CustomColor.ForegroundColor };
}

// change the button color on navigation bar
UINavigationBar.Appearance.TintColor = CustomColor.ForegroundColor;

When submitting the app to Windows Store, the submission will typical fail within 5 minutes after pre-processing complete. The following error message is what shown:

This submission failed with error code(s) 1201 . More info about the error(s) can be found here.

Quick online search mention about using old Microsoft.NETCore.UniversalWindowsPlatform may caused this problem, but I’m using the latest version 6.2.8 which doesn’t have this problem. The certification team told me to resubmit the app because this might be just some random issue on the server, which I did and fail again. I recompile the whole package again and submit to Windows Store. Well, everything went wel…. crash, crash, crash!

Now certification team told me that my app crash on startup which I was not able to reproducible at all using the same package I submitted to Windows store. I even tested it on multiple different machine which different language and region configuration. So I did the same trick of recompile and submit. The app still crash on startup when certification team tried the app. Here are the stack track captured in crash report, although it make no sense to me.

appname::app onlaunched()
stowed_exception 80131500: stowed_exception
combase.dll    RoOriginateLanguageException() error.cpp:1504
System.Private.Interop    System::Runtime::InteropServices::ExceptionHelpers OriginateLanguageException() ExceptionHelpers.cs:113
System.Private.Interop    System::Runtime::InteropServices::ExceptionHelpers GetHRForExceptionWithErrorPropogationNoThrow() ExceptionHelpers.cs:219
System.Private.Interop    System::Runtime::InteropServices::McgMarshal GetHRForExceptionWinRT() McgMarshal.cs:1239
appname.UniversalWindows.McgInterop.dll    __Interop::ReverseComStubs.Stub_12_System __Canon_$catch$0() SharedStubs.g.cs:11147
mrt100_app.dll    RhpCallCatchFunclet2() exceptionhandling.asm:438
mrt100_app.dll    System::Runtime::EH DispatchEx() ExceptionHandling.cs:683
mrt100_app.dll    System::Runtime::EH RhThrowEx() ExceptionHandling.cs:552
mrt100_app.dll    RhpThrowEx2() exceptionhandling.asm:198
System.Private.Interop    System::Runtime::InteropServices::McgMarshal ThrowOnExternalCallFailed() McgMarshal.cs:1267
appname.UniversalWindows.McgInterop.dll    __Interop::ComCallHelpers Call() SharedStubs.g.cs:8527
appname.UniversalWindows.McgInterop.dll    Windows::UI::Xaml::Controls::IFrame__Impl::Stubs Navigate() ImplTypes.g.cs:158360
appname.UniversalWindows.McgInterop.dll    Windows::UI::Xaml::Controls::Frame Navigate() SafeTypes.g.cs:44489
appname.UniversalWindows.exe    appname::App OnLaunched() App.xaml.cs:76
System.Private.Threading    System::Progress$1_$89_System::VoidValueTypeParameter_.System.IProgress_T_ Report() SafeTypes.g.cs:23264
appname.UniversalWindows.McgInterop.dll    __Interop::ReverseComStubs.Stub_12_System __Canon_() SharedStubs.g.cs:11130
appname.UniversalWindows.McgInterop.dll    Windows::UI::Xaml::IApplicationOverrides__Impl::Vtbl OnLaunched__n() ImplTypes.g.cs:138287
Windows.UI.Xaml.dll    DirectUI::FrameworkApplicationGenerated OnLaunchedProtected() frameworkapplication.g.cpp:502
Windows.UI.Xaml.dll    DirectUI::FrameworkView OnActivated() frameworkview_partial.cpp:267
Windows.UI.Xaml.dll    Microsoft::WRL::Details::DelegateArgTraits_long (__cdecl Windows::Foundation::ITypedEventHandler_impl_Windows::Foundation::Internal::AggregateType_Windows::UI::Core::CoreWindow *,Windows::UI::Core::ICoreWindow *_,IInspectable *_ *)() event.h:245
Microsoft::WRL::InvokeTraits_-2_::InvokeDelegates__lambda_3ad0adb09957fd62cbc86618ebbeb8fa_,Windows::Foundation::ITypedEventHandler_Windows::ApplicationModel::Core::CoreApplicationView *,Windows::ApplicationModel::Activation IActivatedEventArgs *_ _() internalevent.h:119
twinapi.appcore.dll    Windows::ApplicationModel::Core::CoreApplicationView Activate() coreapplicationview.cpp:545
rpcrt4.dll    Invoke() invoke.asm:183
rpcrt4.dll    Ndr64StubWorker() srvcall.cxx:392
rpcrt4.dll    NdrStubCall3() srvwrap.cxx:166
combase.dll    CStdStubBuffer_Invoke() stub.cxx:1446
rpcrt4.dll    CStdStubBuffer_Invoke() ndrfwds.cxx:182
combase.dll    ObjectMethodExceptionHandlingAction__lambda_c9f3956a20c9da92a64affc24fdd69ec_ _() excepn.hxx:87
combase.dll    DefaultStubInvoke() channelb.cxx:1452
combase.dll    SyncServerCall StubInvoke() servercall.hpp:826
combase.dll    ServerCall ContextInvoke() ctxchnl.cxx:1418
combase.dll    ASTAInvokeInApartment() applicationsta.cpp:470
combase.dll    AppInvoke() channelb.cxx:1182
combase.dll    ComInvokeWithLockAndIPID() channelb.cxx:2290
combase.dll    ThreadDispatch() chancont.cxx:416
combase.dll    ModernSTAState HandleMessage() modernsta.cpp:472
combase.dll    ModernSTAWaitContext HandlePriorityEventsFromMessagePump() modernsta.cpp:1550
Windows.UI.dll    Windows::UI::Core::CDispatcher ProcessMessage() dispatcher.cpp:339
Windows.UI.dll    Windows::UI::Core::CDispatcher WaitAndProcessMessagesInternal() dispatcher.cpp:1953
Windows.UI.dll    Windows::UI::Core::CDispatcher WaitAndProcessMessages() dispatcher.cpp:461
twinapi.appcore.dll    _lambda_643db08282a766b00cec20194396f531_ operator() coreapplicationviewagilecontainer.cpp:1145
SHCore.dll    _WrapperThreadProc() thread.cpp:321
ntdll.dll    RtlUserThreadStart() rtlstrt.c:1152

Contacted certification support team, but the certification support team insist that I should contact the developer support team. Contacted the developer support team, but the developer support team insist that I should contact the certification support team. In the end, both doesn’t even provide any help or direction and keep quiet.

Long story, I rollback some changes and resubmit the app, everything went smooth. But none of the code I rollback look suspicious at all. In fact they aren’t. Add back the code and everything went hair wired again. In fact, during the app package compilation, .NET native toolchain start to fail, but I usually ignore them because they can be resolve by recompile again. In the end, I emailed .NET native team for help. This is what I get back.

We have seen similar symptoms when the compiler runs out of memory while compiling the app. Sometimes apps are on the edge, and timing around how memory is allocated is all that makes the difference between success and failure.

We have a 64 bit compiler available that can operate with more memory. Can you try to add <Use64BitCompiler>true</Use64BitCompiler> to a PropertyGroup in your main CSPROJ file?

You should be able to validate that it’s doing the right thing by enabling diagnostic build output in Visual Studio, switching build configuration to Release and building the project. In the build log, there should be a line with nutc_driver.exe in it. The nutc_driver.exe that was invoked should be in a tools64 directory (as opposed to the tools directory used by default).

-Michal

Adding Use64BitCompiler is a life saver! It totally work and the app went through submission without a problem at all minimum problem. Gosh, that took long enough! This is the few thing I learn:

• Windows Store will re-compile your package submitted. I never knew that, I though they just testing the package procvided.
• UWP app can grow big very quickly espcially if you use a lot of nuget libraries.
• Bad archtecture design will cause .NET native to run to limitation much quicker, such as two view model is refering each other directly.
• We really need a 64 bits Visual Studio.
• If app submission still hitting error 1201, resubmit again until it success.

• Image reference “Resources\Images\Logos\store_logo.png”: The image “s:\t\7E7C79\appcert_2A0C\7463Ooiks.Bugko-MTGTool_5.8.8.0_neutral_split.scale-100_t9y74dhqw19zm\Resources\Images\Logos\square_71x71_logo.scale-100.png” failed the size restrictions of 50 X 50.
• Image reference “Resources\Images\Logos\store_logo.png”: The image “s:\t\7E7C79\appcert_2A0C\7463Ooiks.Bugko-MTGTool_5.8.8.0_neutral_split.scale-125_t9y74dhqw19zm\Resources\Images\Logos\square_71x71_logo.scale-125.png” failed the size restrictions of 62 X 62.
• Image reference “Resources\Images\Logos\store_logo.png”: The image “s:\t\7E7C79\appcert_2A0C\7463Ooiks.Bugko-MTGTool_5.8.8.0_neutral_split.scale-150_t9y74dhqw19zm\Resources\Images\Logos\square_71x71_logo.scale-150.png” failed the size restrictions of 75 X 75.
• Image reference “Resources\Images\Logos\store_logo.png”: The image “s:\t\7E7C79\appcert_2A0C\7463Ooiks.Bugko-MTGTool_5.8.8.0_neutral_split.scale-400_t9y74dhqw19zm\Resources\Images\Logos\square_71x71_logo.scale-400.png” failed the size restrictions of 200 X 200.

What? The logo submitted was not in the correct size? I never changes the logo in this update and all previous submission went without any problem, why now? Wait, it point to the incorrect image instead. But why? Clean build, delete bin and obj folder then rebuild. Run Windows App Cert Kit locally, yet still fail with the same error after submit.

After some search online, found this post in the forum mention about Resource Map issue when building project in Visual Studio. But the post didn’t mention how to check the resource map. Search online about Visual Studio / UWP resource map get me no where.

Hey, let’s unzip the installation package and see if I can figure out something.

1. Unzip the app upload package (with .appxupload extension).
2. Go into the unzipped folder.
3. Unzip the app bundle package (with .appxbundle extension).
4. Go into the unzipped folder.
5. Here you should find the app installation package (with .appx extension) build for different platforms. For example, mine have: x86, x64 and ARM.
6. Unzip each of the installation package (with .appx extension).
7. Compare the file unzipped from each platform. All platform should have the same number of files inside (You can use tool like Beyond Compare to do the hard work of comparing).
8. In my case, x86 package is missing one file, which is e_sqlite3.dll. This is the problem.

Fast forward, I recently moved the reference of SQLite library in the project from Visual Studio SQLite Extension to nuget package for DevOps purposes. I though that was the problem, but it wasn’t. Actually it was just a simple miss selection that I wasn’t notice when create app packages (I don’t even remember I changed them). Under the x86 architecture, the solution configuration was changed from “Release (x86)” to “Release (Any CPU)“. That is the problem. Switching back to “Release (x86)” and the problem go away.

Gosh, this error really caught me out of no where. Wasted a day staring on the app packaging.

No crash report recorded on App Center (crash analytical tool I used) or Google Play Console which is understandable because whole OS is down). This make the debugging almost impossible since I cannot duplicate this on my phone nor emulator I tried. Since only 1 user reported, I suspect this is very much a isolated case.

After some deep search on the internet. It seem like Samsung Android phone have this cache partition that help app launch faster by caching some data in it. Some time it will become corrupted and causing random problem. Since wiping the cache partition doesn’t wipe any of the user data, I tell my user to give it a try. It work!

Here are the post on how to wipe the cache partition: https://us.community.samsung.com/t5/Phones/How-to-wipe-the-Cache-Partition-on-your-phone-or-tablet/td-p/12662