I checked a couple of tutorials and then dove in to Refactor>Migrate to AndroidX. I imported ActivityCompat, ContextCompat and DrawableCompat.
But now I am stuck getting a compile completed because of this error:
AAPT: C:\Program Data\Android\QiewProjects\DBQiew\app\build\intermediates\incremental\mergeDebugResources\merged.dir\values-v31\values-v31.xml:3: error: resource android:color/system_neutral1_1000 not found.
C:\Program Data\Android\QiewProjects\DBQiew\app\build\intermediates\incremental\mergeDebugResources\merged.dir\values-v31\values-v31.xml:4: error: resource android:color/system_neutral1_900 not found.
C:\Program Data\Android\QiewProjects\DBQiew\app\build\intermediates\incremental\mergeDebugResources\merged.dir\values-v31\values-v31.xml:5: error: resource android:color/system_neutral1_0 not found.
.
.
.
It continues on for about 21 missing items. It appears AndroidX is looking for color files that are missing.
I have spent hours looking for a similar posting, but there aren't any. I have even tried Invalidate caches/Restart but that changed nothing.
Please point me to an explanation to find the missing files or disable the hunt for them. BTW I am using Studio 4.1.2 and compile and target SDK versions 29.
It turned out I had to revise the compile and targetSDK versions from 29 to 31.
It was not mandatory, but I also upgraded the following versions in app/build.gradle:
androidx.appcompat.appcompat:1.0.0 -> 1.4.1
androidx.core.core:1.0.0 -> 1.7.0
androidx.constraintlayout.constraintlayout:1.1.2 -> 2.1.3
Related
I have seen this issue commonly since I started the transition to Julia v0.7 from v0.6. I am getting the following warning:
Warning: Package xxxxx does not have POMDPSimulators in its dependencies:
│ - If you have xxxxx checked out for development and have
│ added POMDPSimulators as a dependency but haven't updated your primary
│ environment's manifest file, try `Pkg.resolve()`.
│ - Otherwise you may need to report an issue with xxxxx
└ Loading POMDPSimulators into xxxxx from project dependency, future warnings for xxxxx are suppressed.
I do not understand why I get this warning. In one of my files, I do: using POMDPSimulators. Since I typed in that, I have done a resolve in the Pkg manager, and done a build POMDPSimulators in the package manager. This doesn't change the warning. How can I get rid of this warning?
Note: xxxxx is just the name of a file/project that is removed to make this post general.
Note: I asked a similar question here: [Julia ERROR: LoadError: ArgumentError: Package xxxx does not have ExcelReaders in its dependencies:
I already checked out the Julia documentation and did what it says. I added the package to the project by using the package manager and typing add POMDPSimulators.
Any suggestions to resolve this issue?
Note: If possible, I am looking for a general answer since I think I am going to have this issue with other packages as well. If there is any other documentation out there besides what was provided by JuliaLang I could appreciate that since I didn't find it helpful.
Link to the Julia Article about dependencies
I tried a pkg> update, build, and resolve. The issue isn't resolved. I see the file in my Manifest and Project file.
Here is what got the Warning to no longer show for me.
Go to your require file and type "NameOfPackageGivingWarning" on a new line.
Click "]" in Julia to open the package manager in Julia command line version:
up NameOfPackageGivingWarning
build NameOfPackageGivingWarning
resolve
activate NameOfPackageGivingWarning
This should resolve the issue for you. I am honestly unsure why this works and I may be taking more steps than necessary, but it resolved the issue for all of my package dependency warnings!
I am having trouble at getting the example "QuickJournal" to compile on iOS. The code compiles OK, but fails during the Fody step.
Goals
Try out the example application for .NET through the following
- Pull the repository
- Open the solution in examples/QuickJournal
- Compile and test
Expected Results
Smooth compilation & testing experience
Actual Results
Fody out of memory exception
Steps to Reproduce
See the setup, follow steps
I am using the latest Xamarin/Visual Studio Mac/XCode
Code Sample
The regular realm source code
Version of Realm and Tooling
git clone https://github.com/realm/realm-dotnet.git
git checkout 8f5e36ffd91e06b9c60b91f9de3fb312b411a4a4
The exception I am getting is
Fody: Found debug symbols at '~/realm-dotnet/examples/QuickJournal/QuickJournal/obj/Debug/QuickJournal.pdb'.
MSBUILD : error : Fody: An unhandled exception occurred:
MSBUILD : error : Exception:
MSBUILD : error : Out of memory
MSBUILD : error : StackTrace:
MSBUILD : error : at (wrapper alloc) System.Object:AllocVector (intptr,intptr)
MSBUILD : error : at Microsoft.Cci.Pdb.MsfDirectory..ctor (Microsoft.Cci.Pdb.PdbReader reader,
See log file
RealmCompilelog.txt
Realm 1.2.1 addresses that by using an updated version of Fody.
Answer for older Realm versions:
This is caused by a Cecil bug with Mono 5.0. As Realm depends on Fody, which uses Cecil, compilation will fail for project referencing it. Until new Cecil and Fody versions are released, the workaround is to revert to Mono 4.8:
I have updated my gnat to the latest version from AdaCore and trying to rebuild the latest AWS (Ada Web Server) also downloaded from AdaCore. I got some errors when building:
aws-services-web_block-context.ads:106:21: argument of pragma "SUPPRESS" is not valid check name
aws-services-web_block-context.ads:106:21: argument of pragma "SUPPRESS" is not valid check name
compilation of aws-services-web_block-context.adb failed
compilation of aws-services-web_block-registry.adb failed
gprbuild: *** compilation phase failed
make: *** [build-native] Error 4
What could have been wrong? Or, have I overlook something?
Thanks.
Adrian
The check that is invalid is Tampering_Check, which is to do with the resource-intensive ARM-specified checks on improper use of Containers (basically, is one part of the code trying to change the structure of a Container that another is already using?)
I don’t know why you’ve had this problem: both GNAT GPL 2016 and FSF GCC 6.1.0 are OK with the pragma. Are you sure you’re using the latest compiler?
One other thing to watch out for is that the master branch at Github may rely on compiler features not available in compiler releases available to unsupported customers; if using GNAT GPL 2016, maybe the gpl-2016 branch would be safer, if not up to date.
After upgrade XCode from 4.2 to 4.3 I've got below problem. I can't build it.
Do you guys have idea how can I resolve this problem? even some clue would be helpful to me.
ld: warning: ignoring file /Applications/Xcode.app/Contents/Developer/Library/Frameworks/SenTestingKit.framework/SenTestingKit, missing required architecture armv7 in file
Undefined symbols for architecture armv7:
"_STComposeString", referenced from:
-[NSMutableURLRequest_ParametersTest verifyDefaultParametersForRequest:] in NSMutableURLRequest+ParametersTest.o
-[NSMutableURLRequest_ParametersTest verifyModifiedParametersForRequest:] in NSMutableURLRequest+ParametersTest.o
-[NSMutableURLRequest_ParametersTest verifyEmptyParametersForRequest:] in NSMutableURLRequest+ParametersTest.o
-[NSString_URLEncodingTest testURLEncodedString] in NSString+URLEncodingTest.o
-[NSURL_BaseTest testURLStringWithoutQuery] in NSURL+BaseTest.o
-[OAHMAC_SHA1SignatureProviderTest testSignClearText] in OAHMAC_SHA1SignatureProviderTest.o
-[OAMutableURLRequestTest testGenerateNonce] in OAMutableURLRequestTest.o
...
"_OBJC_CLASS_$_SenTestCase", referenced from:
_OBJC_CLASS_$_NSMutableURLRequest_ParametersTest in NSMutableURLRequest+ParametersTest.o
_OBJC_CLASS_$_NSString_URLEncodingTest in NSString+URLEncodingTest.o
_OBJC_CLASS_$_NSURL_BaseTest in NSURL+BaseTest.o
_OBJC_CLASS_$_OAHMAC_SHA1SignatureProviderTest in OAHMAC_SHA1SignatureProviderTest.o
_OBJC_CLASS_$_OAMutableURLRequestTest in OAMutableURLRequestTest.o
_OBJC_CLASS_$_OAPlaintextSignatureProviderTest in OAPlaintextSignatureProviderTest.o
_OBJC_CLASS_$_OARequestParameterTest in OARequestParameterTest.o
...
"_OBJC_METACLASS_$_SenTestCase", referenced from:
_OBJC_METACLASS_$_NSMutableURLRequest_ParametersTest in NSMutableURLRequest+ParametersTest.o
_OBJC_METACLASS_$_NSString_URLEncodingTest in NSString+URLEncodingTest.o
_OBJC_METACLASS_$_NSURL_BaseTest in NSURL+BaseTest.o
_OBJC_METACLASS_$_OAHMAC_SHA1SignatureProviderTest in OAHMAC_SHA1SignatureProviderTest.o
_OBJC_METACLASS_$_OAMutableURLRequestTest in OAMutableURLRequestTest.o
_OBJC_METACLASS_$_OAPlaintextSignatureProviderTest in OAPlaintextSignatureProviderTest.o
_OBJC_METACLASS_$_OARequestParameterTest in OARequestParameterTest.o
...
ld: symbol(s) not found for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)
I was getting the same linking error for the Simulator after upgrading from Xcode 4.2 -> 4.3.1. I noticed that new projects in 4.3.1 do work with Unit Tests, so just compared the project differences.
What fixed it for me was:-
Select Project in project navigator
Select Test Target
Select Build Settings
Go down to Framework Search Paths and single-click it
Delete whatever is there
Enter $(SDKROOT)/Developer/Library/Frameworks $(DEVELOPER_LIBRARY_DIR)/Frameworks
If you had any custom frameworks, add those back
Actually, Unit Tests run fine on the Device, too.
Looks like this was either an accidental (or on purpose) omission on Apple's part.
If (and only if) you are a registered Apple Developer, you can log into the Apple Developer Forums and if you copy this linked search query into your browser address bar, you will see other people have had the same problem.
For now, it looks like you can only use SenTestingKit on the simulator.
I had a similar issue with Xcode 4.4.
My solution path:
Removed SetTestingKit.framework from the main target's (the system under test) "link binary with libraries", leaving it in the test target as is. Not sure why it ended up there in the first place.
I believe this bug is now fixed in Xcode 4.4.1
Using xcode 4.6 and trying to add facebook SDK 3.1 I had this problem because I didn't select to add the files to my test target.
You should check both targets when you copy the framework.
I just upgraded to 4.3.1 There is a problem with SenTestingKit framework. I removed the test source code from the project, it builds ok. And it can run on 5.1 device. But I got _dyld_dyld_start error when I ran it on simulator. I had to remove SenTestingKit from the project to make it work on simulator.
I am trying to setup a Flex/Java multi module project in Eclipse. Using Maven to run the build and generate the war file. The details of the versions I am using are as follows:
Flexmojos : 3.5.0
Flex framework/compiler : 4.5.1.21328
Target player : 10.2.0
And the playerglobal dependency in my pom file uses classifier as 10.2 with version 4.5.1.21328
Now when I run the build using 'mvn install', I get the following error:
[ERROR] Failed to execute goal
org.sonatype.flexmojos:flexmojos-maven-plugin:3.5.0:compile-swf
(default-compile-swf) on project client: TargetPlayer and
playerglobal dependency version doesn't match! Target player: 10.2.0,
player global: 10.2 -> [Help 1]
Any ideas why this might be happening?
I tried just playing around changing those version numbers, but still couldn't make it work for Flex 4.5.1. Please let me know how to go about this (and if you need more information). Thanks.
Regards
Basith
Have you tried simply referencing "10.2" instead of "10.2.0"? I think there was only one Flash player deployed with a 3-segment version number.