I have just updated to Android Studio 3.1.1, and now all my support library related imports are shown as broken (see screenshot attached), even though the app successfully builds and can be installed on a device. Is there a way to fix this? Thanks.
I had the same problem also
and resolved it by using support version 27.1.1.
Indeed, using support library version 27.1.1 fixed the problem.
Thanks, whoever commented and then deleted their comment - good thing I noticed it :)
Related
This is the error. As shown in the image. This is not letting the app run.
This happens when I set the compile sdk version to 33. What to do?
Thanks in advance.
You can either ignore it or upgrade to Android Studio - Dolphin; it is a known bug. I had literally hundreds of these Unknown Attribute errors in my project, but they went away when I upgraded to Dolphin v2021.3.1.
Here's a link to Google's issue tracker indicating it is resolved in Dolphin: https://issuetracker.google.com/issues/241460885
I'm using WinRT C# application and after a Windows update 20H2 (framework: 528372), the syncfusion Scheduler component stopped working and crashes the application. On Windows 1909 (framework: 528040) it works correctly
The error: Cannot create instance of type 'Syncfusion.UI.Xaml.Schedule.ScheduleAppointmentEditor'
I updated the libaries to a newer version which didn't solve my issue.
I currently have two versions of the same application
WinRT
UWP
The UWP works fine on 20H2 Windows versions and both UWP and WinRT apps have the same libaries for the syncfusion.
Any workaround that I can put in place to make it work again on version 20H2?
Regarding Cannot create instance of type 'Syncfusion.UI.Xaml.Schedule.ScheduleAppointmentEditor
The reported issue has been fixed and included in the patch which can be download from the below links.
Recommended approach - exe will perform automatic configuration.
Please find the patch setup from below location:
Patch link:
https://syncfusion.com/Installs/support/patch/14.4.0.15/1015043/F168937/SyncfusionPatch_14.4.0.15_1015043_9272021085339206_F168937.exe
Please find the patch assemblies alone from below location:
Assemblies Link: https://syncfusion.com/Installs/support/patch/14.4.0.15/1015043/F168937/SyncfusionPatch_14.4.0.15_1015043_9272021085339206_F168937.zip
Nuget link: https://syncfusion.com/Installs/support/patch/14.4.0.15/1015043/F168937/SyncfusionNuget_14.4.0.15_1015043_9272021085339206_F168937.zip
Disclaimer:
Please note that we have created this patch for version 14.4.0.15 specifically to resolve the issue reported in this incident.
Syncfusion gave an updated library with the fix. Issue Resolved
Heres the link, version 14.4.0.15 but this is specific to this issue as i could read : https://www.syncfusion.com/forums/168937/cannot-create-instance-of-type-syncfusion-ui-xaml-schedule-scheduleappointmenteditor
After this huge mess from one AndroidStudio update, am cleaning everything and starting from scratch.
I'd like to ask if anyone knows if I should go with specific versions of Java.
But first my headache, although I just cleaned my computer of AndroidStudio.
I have Win 10 64 bit
HAD AndroidStudio 1.51 (it said it was JRE:1.7.0_79-b15 amd64)
After the update I had a "Unsupported major.minor version 52.0" error
Following some posts I upgraded the Java on my machine.
First "1.8.0_74" but AndroidStudio couldn't find the JDK directory, so I installed "1.8.0_73" and AndroidStudio found the JDK directory. But then I started getting rendering errors but with Rendering Problems Exception raised during
rendering: com.android.ide.common.rendering.api.LayoutlibCallback.getXmlFileParser(Ljava/lang/String;)Lorg/xmlpull/v1/XmlPullParser;
Anyway, that's it. This has become such a tragedy that I would rather start from scratch, but if anyone could point me as to the proper (steps) of which way I should go, I would really appreciate it.
Thanks ahead,
Sergio
I met this issue when I updated the api android 23 N (preview). In xml editor, change the Api to render into Api 23 android 6.0 and Autimatically Pick best.This would solve the problem.
refer: link
Yes.. i also faced same problem,I have resolved with changing the version to api 23.generally it will take best/latest version ,in my case its set to N preview.
I've encountered a problem after upgrading from Visual 2015 RC to Full version. Fody.PropertyChanged doesn't work in UWP (it worked with RC). After using reflector there is no raisepropertychanged injection, no warnings, nothing. Any ideas?
EDIT: it doesn't even create FodyWeavers.xml after installing it with new Nuget.
The reason is that Nuget deprecated several features for Universal Projects
See here for the full details https://github.com/Fody/UniversalAppSample/
When I try to add a service reference to my project in Visual Studio I keep getting the error " The parameter is incorrect" I know it's not the code because it doesn't happen on my coworkers computer. I have uninstalled and reinstalled Visual Studio to see if the problem is with my installation. But that doesnt seem to fix it.
I am using visual Studio 2012.
Did anyone come across this issue before? Please help!
I had this problem with a project that was copied out of ClearCase. the .csproj file still had the reference telling visual studio that its still under CC. I removed the following references and it worked.
<SccProjectName>Rational ClearCase</SccProjectName>
<SccLocalPath>Rational ClearCase</SccLocalPath>
<SccAuxPath>Rational ClearCase</SccAuxPath>
<SccProvider>Rational ClearCase</SccProvider>
I had the same issue after updating SQLite plugin for windows phone.
It seems like the sqlite-net-wp8 project (which is a wrapper to work with the plugin) had some import method from that plugin and when the version changed the wrapper didn't work anymore.
The solution was to downgrade the sqlite plugin to a version that is compatible with the wp8 wrapper.
Edit: The wrapper had an update so I've upgraded both the plugin and wrapper and now the issue is fixed.
If it shows any project in your solution with "(failed)" next to it's name try to remove it and re-add it to your solution and it will tell you what the issue exactly is.
In addition to Frisons answer - the issue works aswell the other way round:
If you are using ClearCase, make sure that the entries mentioned by Frison are available in your project file. I just had this case that one of the projects in my solution did not (however) had these entries and i got the very same error. Adding these lines fixed this issue for me.
I got the same error for WindowsPhone project, after make a clear manifest the error disappeared.