AEXML | Swift minion for simple and lightweight XML parsing

Created a Swift Package (// swift-tools-version:5.3.0) for an XCFramework. The package has dependencies on 4 other Swift packages (2 of them using swift-tools-version < 5 and 2 are >= 5.0). It builds and runs in the project's Demo app target. The generated XCFramework copied into a Swift Package repo and hosted on GitHub.

I then create a new project and the Swift Package can be successfully imported into it thru SPM. The dependencies are also imported.

When building the new project, my framework fails to compile due to an error in my framework's generated .swiftinterface file, 'XMLIndexerDeserializable' is not a member type of 'SWXMLHash':

Can anyone shed some light on this failure? Not sure if it an issue with my packaged framework, a config issue with the new project that imports it, or an error due to the difference in the Swift tools version of the dependencies.

Some Background Details On My Config and Process

My Swift Package config:

I will try to explain my problem in brief here. Please refer to the github link for my project if my explanation here not enough. Github link

I have a horizontal recycler view inside a vertical recycler view. I've on click listeners for the vertical items and that just works fine.

I want to also have an onClickListener for the horizontally scrolling list. But the app crashes when I implement the same for it.

I've implemented the click listener using an interface in the adapter and implementing the interface in the fragment/activity.

I am initializing the horizontal recycler view and the adapter for it inside the main adapter and not in the activity code.

I am getting the following error

java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.content.Context.getPackageName()' on a null object reference

I am trying to use Alamofire to upload a multipart form. The form has to have two parts, the .IPA file which is saved to my desktop and an xml which includes some properties. The XML I am creating using AEXML which outputs an XML as a string. The alamofire upload seems to want a URL for each but I am not sure how to convert. "outputFile" is a string path location of the .IPA on my desktop and "xmlString" is the xml. Below is my code:

I want to parse a XML from URL which is RSS of my blog with SWXMLHASH or AEXML libraries. I found a solution for this but when I tried the solution my app crashed. It is the encountered problem:fatal error: unexpectedly found nil while unwrapping an Optional value (lldb)

And there are my codes which are in viewDidLoad:

I am using a XMLParser Library. I have a xmlDoc and I don't know how can handle some tag values. For example:

My question is in two folds - the first part is choosing the appropriate XML parser and the second part is a question about a proper way to handle the parsed data.

I need to parse two XML files from the web. One file contains ~200K lines and the other one contains ~10K lines. The data is used in populating three TableViewControllers. I have been researching on XML parsers and have read several posts on StackOverflow, but I'm still confused about which one to choose.My research led me to believe that either SWXMLHash or AEXML is suitable for my situation. SWXMLHash seems to be a good choice for parsing large XML file (with lazy loading option) but I need to use Alamofire since it can't handle URL request. But when I look at Alamofire examples, I'm under the impression that the requested file is returned as a whole through callback function call. If I understand correctly, that means the whole file is stored in memory. (So what's the point of lazy loading of SWXMLHash if the file is already in memory?) So I look into AEXML examples, but seems that it is not even async library and it also loads the data into memory. So which library should I be looking into for parsing those XML files?

One approach I thought of on handling parsed data is to store them in core data and query the core data when I need to populate the TableViewControllers. The core data needs to be updated on daily basis since the XML files on the server are updated daily. If the user does not have data with today's datestamp, I'll just drop the existing tables, download the new XML files, parsed them and create two new tables with that parsed data. Does that approach efficient/reliable?

UPDATE :

I was wrong about AlamoFire. It does have a method that downloads the file and stored it on the disk in addition to those methods that return data in the response variable. So parsing, I decide to use combination of SWXMLHash and AlamoFire.