You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I can tell, this (very much improved in many ways) new version of TBXML assumes all XML files processed will be contained in the application bundle. That is absolutely a show-stopper for my requirements as I use XML files for all manner of communication between clients and server - most of which are never located "in the app bundle'.
I will implement my own work-around but it would be wonderful if this capability were incorporated into the official source code.
Thanks much!
The text was updated successfully, but these errors were encountered:
I use the latest TBXML in multiple apps solely for parsing of network API replies. I've never used it to parse files in the app bundle. Maybe post some code that's not working for you?
Doesn't need an example, try to download a file, store it on the app's Documents folder, and try to read it afterwards.
I cannot understand why bothering to have so much work splitting paths and extensions to obtain a file from app's bundle, if a simple path could be work for all.
From what I can tell, this (very much improved in many ways) new version of TBXML assumes all XML files processed will be contained in the application bundle. That is absolutely a show-stopper for my requirements as I use XML files for all manner of communication between clients and server - most of which are never located "in the app bundle'.
I will implement my own work-around but it would be wonderful if this capability were incorporated into the official source code.
Thanks much!
The text was updated successfully, but these errors were encountered: