I have an app I have been working on that was running fine.
I upgraded to the latest Xamarin with mac support and now I get an error when I try to use HttpUtility.ParseQueryString.
I have an App.config file and it is telling me that it can't parse it, but this happens when trying to call ParseQueryString. How are those 2 related?
I thought I had found the problem because my app also has a ServiceReferences.ClientConfig file for http client settings. I copied my App.config section to the ServiceReferences.ClientConfig file and that fixed it until I went to show my fellow dev the new error.
The new error was saying something about Path.Combine path1 being null.
I looked up that error and found a reference to a page talking about MacSupport in xamarin here: https://searchcode.com/codesearch/view/8556026/
I don't know if they are related, but that is the closest I found to the stack trace I was seeing.
Can anyone tell me what changed in Mono 4.8 for Mac in Xamarin that would cause an issue with HttpUtility.ParseQueryString and how to solve it?
System.Configuration is a common point of pain during mono upgrades, as it's behavior sometimes subtly (or not so subtly) changes.
You'll need to post a much larger chunk of information here for anyone to be able to help you.
Or you could post on the XM Forms or file a bug if you believe this is a bug, as those are a more appropriate place for such reports.
Related
I've spent the last two days trying to submit my app to the App Store. I get the message below:
ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/Flutter.framework/Flutter: _kCTFontOpticalSizeAttribute. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/
Here's what Ive done so far:
a) I've scoured my code for any reference to Font Sizes - I had some that were constants - I changed the constant name to:
k_fontSizeMyName
b) I tried to download the latest flutter sdk version
c) I rebuilt my entire keychain.
Im so desperate right now. im tired.
What do I do?
the internet has no mention of this bug.
I've got the same message several times from the App Store Team a few minutes ago.
I think the problem was the Flutter SDK version...!
I used to use the latest version(Flutter SDK version 1.12.3-pre.26) at first but changed the Flutter SDK version to 'v1.9.1+hotfix.3' and the problem is resolved!!!
I solved the problem with the following instruction below:
Switching Flutter SDK version to 'v1.9.1+hotfix.3' with the command:
flutter version v1.9.1+hotfix.3
Archive and upload again ...
Problem Solved!!!!!! 🤩
This may be a recently-introduced Skia regression.
The code was included in Flutter v1.12.3, so v1.12.2 on the dev channel should work.
Flutter's Bad Build wiki page will be updated when there is a fix for this issue.
Update: This has been resolved in Flutter v1.12.5.
Since there have been a lot of problems with flutter recently(when I tried the fix mentioned in another answer I different error) I though I should include this https://github.com/flutter/flutter/releases
Just type flutter version [version code]
I am getting the following error when I attempt to compile in release mode to put my application in the Android App Store. I do not get the error when I compile for debug mode.
I have found references to similar errors. They seem to revolve around the android support services not matching the Android SDK. I am running on the Android 28 SDK. I have updated my google support libraries to the v28.0.0 in NuGet. I am running in macosx and am using vs mac.
I am quite at a loss on this issue. Any suggestions are appreciated.
TIA
...../obj/Release/lp/40/jl/res/values-v26/values-v26.xml(0,0): Error APT0000: Error retrieving parent for item: No resource found that matches the given name 'Base.V21.Widget.Design.AppBarLayout'. (APT0000)....
Ok, I'm not sure that I have "solved" the problem completely, but I have at least solved it for the moment. I kept digging into the output and found a funny character in the custom proguard.cfg information in the build output. I opened the proguard.cfg file that I had created in notepadd++. Sure enough, notepadd++ is set to encode with the "UTF-8 with BOM" setting. I changed that, resaved, rebuilt, and no errors. I'm going to keep a watchful eye on this, but the problem for the moment is resolved. Thanks for everyone's input. It was much appreciated. :-)
I should mention that I originally posted this as an issue on Neovim's tracker, but it hasn't been getting a ton of traction there lately and I'm beginning to suspect that it's more an issue with my setup rather than Neovim itself.
Essentially, I had stopped building neovim nightlies for a few months. Having heard that it's getting integrated terminal support I decided to rebuild using the latest source, only to get a persistent, odd error. No matter what my build settings are, it always boils down to make hitting an error when it has to compile a file called loop.so. I hadn't noticed this issue with any other software I try to build, but I suspect it could be an issue with my environment.
Does anyone here know what this file's role is, and why the compilation could be failing at that point?
You might need to install the full Xcode app and not just the command line. This fixed the issue for me.
The issue turned out to be a bad typedef in a libuv header, object.h.
When I tried to use an Ajax control toolkit, I get a grey out error and searching around they said installing VS10 Service pack could help to solve the problem. So I did install it and now I got a serious problem:
I can no longer load the website that I can load normally before, it shows this error:
Server Error. 500 - Internal server error.
I tried many ways and finally found this one looks quite close to what happened to me:
http://support.microsoft.com/kb/842329
And I tried what it suggested:
go to C:\Windows\system32\mcfc42.dll-> properties\security\Edit\Add
Added:
Iwam_computername or computername\Iwam_computername
Also added:
Everyone
Allow Full control to all.
Restart server. But still the same problem. Please help me to fix this problem, unfortunately my server did not install backup option before I install VS SP1 so I could not recover to the previous point. Any solution ? If I cannot access it, no way I can code and test my website...
I found the solution for this. At first, to narrow down the problem I load the website at server side (not at client side) then I see this error lines in my web.config file, I think when I click at property at project in VS and choose .net 4.0 then back to 3.5 it add some duplicate to my web.config file. I just add all the first lines related to .net 3.5 and keep the xml format correct then it works fine now! Many thanks !!
EDIT: It seems like no one knows the answer. New question: can anyone post a step by step tutorial how to create a mac project manually?? The answer to that question will of course get the "tick" as accepted answer..
I have the latest cocos2d version installed.
I made a new mac template and without changing anything I just build it. But I get 26 errors and 7 warnings.
The most important one (I think) is this one:
ld: warning: ignoring file /Developer/SDKs/MacOSX10.7.sdk/Library/Frameworks//OpenAL.framework/OpenAL, file was built for unsupported file format which is not the architecture being linked (x86_64)
I get lots of CDSoundEngine and audio stuff errors.
In the warning I copied above...before the "OpenAL.framework" is a double backslash..strange.
I tried to re-add the OpenAL framework but I get the same error.
I also tried to make a new one but I get the same errors..
I also reinstalled cocos2d..didn't work either.
This only happens with the mac templates...
Does anyone know how to fix this?
Edit: (Added screenshot)
link to screenshot: http://dl.dropbox.com/u/3951219/screenshot_mac_template_error.png
http://dl.dropbox.com/u/3951219/screenshot_mac_template_error.png
A tad late, but I just had the same problem.
For your original question, try this answer here...
My OpenAL Framework is broken
Oh, and btw, the // is normal. It happens when a program opens a directory like {Frameworks}/OpenAL.framework, and "Frameworks" is /Developer/SDKs/MacOSX10.7.sdk/Library/Frameworks/. The OS takes a // as a /