Can't run published Blazor WebAssembly app - progressive-web-apps

The app works just fine when I run it in the Visual Studio debugger, but if I deploy it to a server I get this error in the browser console:
Failed to find a valid digest in the 'integrity' attribute for resource 'http://example.com/pwaexperiment/wwwroot/_framework/wasm/dotnet.3.2.0.js' with computed SHA-256 integrity '80L/hSwps3gjABzV78X6mehoDDgsLkm1pKpSS6fAqiE='. The resource has been blocked.
What does this error mean and how can I fix it?

Try adding the following tag to your project:
<BlazorCacheBootResources>false</BlazorCacheBootResources>
Reference: https://github.com/dotnet/aspnetcore/issues/24505#issuecomment-684857753

Your server may be compressing JS files on the fly, that changes content so integrity fails. Disable compression.

Try to delete the bin and obj folders in the project. Then the compiler will rebuild the blazor.boot.json file with the new hashes. And it loads and passes the hash check on the browser.

Related

Build Visual Studio project fails - The cloud operation was unsuccessful

I'm using two laptops and stored my C# code in OneDrive.
I am aware that sharing code via OneDrive is not be the best approach, but that's what I'm dealing with now.
I noticed that on laptop 1 I have to define the following path to the data file (mdf):
C:\Users\ Diet\OneDrive\Personal\VisualStudio2019\Repos\project\project\App_Data\data.mdf
On laptop 2, the path is different because the user I'm logged in with has a different name (or at least that's what I believe is the cause)
C:\Users\ Dieter\OneDrive\Personal\VisualStudio2019\Repos\project\project\App_Data\data.mdf
Updating this in the Web.config fixed the connection to the database, BUT building the solution still returns an error, also related to a cloud operation, hence why I think it is caused by the path in OneDrive...
The error message:
CSC : error CS0041: Unexpected error writing debug information -- 'The cloud operation was unsuccessful.
I welcome your insights. Thank you for helping me out.
I have my projects stored in OneDrive and had this same issue. The fix was to set the entire Project folder contents to "Always keep on this device".
Seems that building the solution in VS was attempting to write to files that were not cached locally from OneDrive. As soon as I changed the setting, the build worked!
I was also storing my project on OneDrive, got the same error after installing a new ssd.
Rebuilding the solution was enough for me.

TFSBranchToolVsExtension Exection of Action ConnectSourceControl Fails

I downloaded the TFSBranchTool VS Extension Project.
Rebuilt and Installed, but when I try to apply Initial Structure I get the following Error:
Exection Error:
Exection of Action 'ConnectSourceControl' Failed. Details: Could not load file or assembly Microsoft.AlLMRangers.BranchTool.SourceControlWrapper......
Any idea what might be causing the problem ? I tried on 2 different Servers! , I got the latest Update of VS2012.
I got VS2012 SDK installed and Vs2012 ObjectModel too, not sure what I'm missing!
We have posted an update to the sample code on http://vsarguidance.codeplex.com/releases/view/96222, which addresses this bug.
The issue was that Microsoft.ALMRangers.BranchTool.SourceControlWrapper.dll was missed in VSIX package. As action execution engine using MEF to load actions, it has no direct references to actions implementation assembly.
Vladimir from the team fixed the issue by specifying assembly as the MEF asset in the VS extension’s manifest file. Now it’s redistributed inside the extension package.
Can you verify that you have the file Microsoft.ALMRangers.BranchTool.SourceControlWrapper.dll
in the following folder:
%LOCALAPPDATA%\Microsoft\VisualStudio\11.0\Extensions\Microsoft. ALM Rangers\TfsBranchToolVSExtension\1.0
If its not there - try deleting the TfsBranchToolVSExtension and re-install the VSIX.

TICoreDataSync with dropbox SDK giving 'path not found' error

I've followed the tutorial found here to set up my app for dropbox sync. When i start the app, thus starting sync, i get this:
[WARNING] DropboxSDK: error making request to /1/metadata/dropbox/com.timisted.notebook - Path '/com.timisted.notebook' not found
[WARNING] DropboxSDK: error making request to /1/metadata/dropbox/com.timisted.notebook/Documents/Notebook - Path '/com.timisted.notebook/Documents/Notebook' not found
And a list of similar errors.
Any ideas what the cause of this is, and how I could fix it?
EDIT: I tried this with the example app provied with TICoreDataSync, using my credentials, and it accepted the credentials but it didn't work.
I've found you can typically ignore these messages. TICoreDataSync will try and make the request and then if it fails, it will create the folder and continue.
Here are the changes I had to make to get iOSNotebook to run:
Dropbox wouldn't let me create an app called “iOSNotebook” as it was already taken (no surprises there :)). So I changed the name of the Xcode project and target to iOSNotebookCA along with the TICDSDropboxSDKBasedApplicationSyncManager's globalAppIdentifier to #"com.timisted.iOSNotebookCA"
Next I had to change Build Settings > Build Active Architectures Only = Yes
I changed the deployment target to 5.1 so I could avoid having all test devices running 6.0 (optional)
I also had to change the info.plist file's URL string to reflect the Dropbox key assigned to my iOSNotebookCA (db-blahblahblah).
And changed the DBSession root to kDBRootAppFolder
We recently released version 1.0.2 of the framework along with updated documentation, example apps, and tutorials on the project wiki. Check it out and if you run into any snags open an issue on the project's Issues page

failed to load RSL textLayout

I just installed gentoo linux amd64.
on that I installed eclipse 4.2M5 with FD5 for flex development.
after compiling my project, when I execute it i get the following in the log file:
Error #2046: The loaded file did not have a valid signature.
Failed to load RSL http://fpdownload.adobe.com/pub/swz/tlf/1.1.0.604/textLayout_1.1.0.604.swz
Failing over to RSL textLayout_1.1.0.604.swz
Error #2046: The loaded file did not have a valid signature.
i use FD5 with Flex 4.1A.
any ideas why it happens ?
update:
it seems that when I close and open my project I am able to execute my project once. the 2nd time that I execute the project on my browser I get the error and I need to close and reopen the browser to execute it again.
First of all thank you for all of your comments.
I finally was able to properly resolve the issue.
it seems that flash saves cache info at ~/.macromedia
(~ for home dir, for example if the user is ufk so it translates to /homeukf)
all I need to do is to delete that folder, since then I am able to refresh my app on the browser without any problems.

How can I fix this Android SDK build problem in Eclipse?

I am using Eclipse for Android dev and everything was going fine until I tried to incorporate the facebook SDK. Now when I tried to back it out, there appears to be an artifact left behind that Eclipse tries to link the FB library?!?
[2010-11-17 18:50:22 - Library Project] Unable to set linked path var '_android_com.facebook.android' for library /Users/mobibob/Projects/workspace/facebook-android-sdk/facebook: Path variable name cannot contain character: ..
Any clue where this command / reference is in the build configuration? I have scoured it as best that I can, but I still get the same error.
Problem solved ... as it turns out, it was not so much the Facebook SDK but something that I did in the process of configuring the library reference. I am not entirely certain of how I misconfigured, but I was tweaking the various "path" settings such that, once when the automatic build tried to build my project, an import for android.R was added to my source module. This superseded com.myproject.R and would not resolve the values for resource references.
There were other problems with path order and setting that I modified during the troubleshooting that made it worse. Recreating the project without Facebook was the first step to discovery and fixing.
Either way, the lesson I learned is that the build error messages can misdirect one to the configuration when the problem is in the source code.