I got this message error:
Inceptionv3.mlmodel: unable to read document
I downloaded the last version of xcode. Version 9.4 beta (9Q1004a)
You don't have the Inception3.mlmodel file. You must get it. Next, drag and drop it to the project. Then you can remove this red file shortcut you already have.
The main problem is to get that file. All pages send you to
https://developer.apple.com/machine-learning/
but Apple doesn't show download, wich previous probably looks like that:
https://cdn-images-1.medium.com/max/1600/1*6agZ1CcGVwiOaX3gNP8cYw.png
I had the same problem with GoogLeNetPlaces. I found some models on
https://github.com/SwiftBrain/awesome-CoreML-models
but to find the file that interested me most I used torrent.
Related
We are using the package receive_sharing_intent in our application, but with recent update of Flutter and the package not being updated for 15 months, the feature implemented does not work well now, especially on iOS, Android is still doing fine until now.
The feature: for every kind of document (PDF, txt, xls, ...) stored in the device or attached to a mail, when you share it with the application, it should open it, process it, and store it in our database.
So we use the package here to retrieve external data and open our application, and that both on Android and iOS.
We still have not found a workaround that lasts over time for this specific case. Let me know if you find a solution while I continue my research.
Thanks in advance.
I spent a few days on this error, finally I found the exact problem I was experiencing, and the solution.
I finally got the error for the .PDF file extension, the path is incorrect. There is a function in the SwiftReceiveSharingIntentPlugin.swift file inside the Flutter package receive_sharing_intent that is supposed to remove the substring "file://" at the beginning of the file path, but for some reason I still have it in my PDF file path, so it could never be found.
To solve this problem, I use the "replaceAll" method in my Flutter code:
file!.path.replaceAll("file://", "")
I updated the title of this post to match the problem I encountered.
I was working on a language translation project in trados on a virtual machine. Half of the work was done and the translated words were exported into a Word docx file. Upon restarting the virtul machine, the project file appears to have been corrupted as trados shows no signs that the project was worked on. When I manually open the sdlproj (trados project) file, trados cannot open the file mentioning the following:
: An error occured whilst trying to determine the file version
I have tried creating a new project and used pre-translate using batch tasks but that did not seem to have imported the previously translated document. I need to figure out how to recover my project so that I can recover the translated document (so I do not have to redo the work) as well as recover the translation memory for trados. The translation memory folder is present inside the original project folder. I would really appreciate any suggestion to further troubleshoot and fix this issue. I have tried their support desk but they do not appear to be available today. Two solutions I observed from their forum suggested:
save the project file with a zip extension, extract the contents and then open the sdlxiff file from there
recreate the project and use pre-translate.
In my case, I was able to open the sdlxiff file from the translated language directory. This opened the project with the text that had previously been translated. I am not certain whether I need to remove the sdlproj file or simply save the project hoping that it will overwrite the corrupted file. In either case, I will update this post once I get an answer to that.
Hi I have a problem I can not find template.pcp file that should be in windows SDK but It is not. I need it to make a patch .msp file I am following this tutorial: MSDN tutorial . Does anyone know where could I find it?
I can't see the template.pcp file anywhere in the SDK at this point, it might have gotten removed whereas it previously kept being moved.
The free MSI SDK tool called Orca can save a PCP file - and other types of MSI-relevant files. Search Windows SDK folder for Orca-x86_en-us.msi and install. Some more info here, current paths etc... (towards bottom).
WiX can also create a PCP file via markup, as explained in this thorough tutorial: Using Patch Creation Properties. This tutorial should contain all required information to succeed without the template.pcp file (though I never use patching).
I am trying to build my app but I received an error that "TapkuLibrary/TapkuLibrary.h" file not found but the file is added to my references.
I am not the one who did this project, this was just past to me without proper turn over.
I actually replaced my laptop and just open my source code from a new one with XCode 7.3.1
I also tried several solutions that I found here but still not working.
I'm also loosing some Link Binaries,
As the title shows, I'm currently facing a problem in which I'm trying to add a Swift file to my ObjC project. The bridging header is generated and as soon as I'm trying to build, it stops with the error:
<unknown>:0: error: opening import file for module 'Swift': Permission denied
This only happens with 1 specific project (which is an old app that has been receiving updates once every year or so). A newer project can implement the swift file and build without any problems. I've compared the build settings but couldn't find any differences (and the ones that were there, eventually didn't cause the error).
I've attempted to remove all the Swift related data in the app and let it get generated again, which didn't work. I've also tried to build on both iOS8 and 8.1, but to no avail.
I'm currently out of ideas on what can cause it and I haven't been able to find anything on StackOverflow or Google in general about it so far.
The only method I've found and eventually have used is by creating a completely new Xcode project and restructuring/importing the old files. I've spent an Apple ticket on this project, but they haven't been able to help me out with this problem either.
So, my answer to this is; Create a new Xcode project if it's too outdated to implement Swift.