I Just download stambia which is a now a product of semarchy (semarchy xDI Designer, I think ?).
I have some difficulties to open the application.
Note that I am using a Macbook Pro (macOs Monterey 12.4)
I have this issue:
I am just an end user here.
I cannot alter the source code.
Related
I wrote a screensaver in Swift.
Although I had set the macOS Deployment Target to macOS 10.13, it failed to run on an x86_64 Mid 2010 Mac Pro running macOS High Sierra 10.13.6.
Meanwhile, it runs fine on my arm64 2020 MBP M1 with macOS Big Sur 11.5.2, and on an x86_64 2019 MacBook Air with macOS Catalina 10.15.6.
The screensaver installs fine on all machines, but on the machine running High Sierra it says that the screensaver is not compatible.
The error message shown is as follows ("vibe" is the name of the screensaver that I made. So anyone else running across this same problem will see a similar message but with the name of their own screensaver in place of that of course):
You cannot use the vibe screen saver with this version of macOS.
Please contact the vendor to get a newer version of the screen saver.
I am wondering if there is a way to automatically figure out if there are any APIs or other features that my code is using which were not available in macOS 10.13. And also I am wondering if it is usual that you can build for a given macOS Deployment Target and then when you try to run the program on a machine that is within the range that should be supported, the program will not run after all. I had thought that there would be a build time error to build for a macOS Deployment Target if the built program will not run on it.
I am using Xcode 12.5.1 running on my MBP M1, macOS 11.5.2, and as mentioned I am building for macOS Deployment Target set to macOS 10.13. The screensaver runs fine on both Intel with macOS 10.15 and ARM with macOS 11.5. I am using Swift Language Version Swift 5.
Solution
Install "Swift 5 Runtime Support for Command Line Tools" from https://support.apple.com/kb/dl1998?locale=en_US on the macOS 10.13 machine I wanted to run the screensaver on.
Background, details and alternative solution
Thanks to the comment of #Alexander, where he suggested:
Have you tried poking around Console.app to see if anything intersting was logged?
I was able to figure it out.
In Console.app, in the default view that shows device messages for the computer, I applied a search filter for any occurence of the name of the screensaver and then in System Preferences > Desktop & Screen Saver, I selected my screensaver and clicked "Preview" hoping that this would result in something in the logs. And it did!
Relevant log message:
Error loading /Users/erikn/Library/Screen Savers/vibe.saver/Contents/MacOS/vibe: dlopen(/Users/erikn/Library/Screen Savers/vibe.saver/Contents/MacOS/vibe, 265): Library not loaded: #rpath/libswiftCore.dylib
Referenced from: /Users/erikn/Library/Screen Savers/vibe.saver/Contents/MacOS/vibe
Reason: image not found
With this in hand, I was then able to find a similar root cause and some suggested solutions at dyld: Library not loaded: #rpath/libswiftCore.dylib / Image not found
Which amount to setting "Always Embed Swift Standard Libraries" to YES, and possibly also adding #executable_path/Frameworks to Runpath Search Paths.
This may be one acceptable way of doing it.
However, not knowing the specifics of how this will interact on other systems and in the future I was a bit hesitant.
Fortunately, I then found https://developer.apple.com/forums/thread/687847 which while not directly relevant directed me to look for "Swift 5 Runtime Support for Command Line Tools", as this would provide the missing libswiftCore.dylib for macOS 10.13.
I am windows user and have no experience with macOS. I have developed flutter app in Windows 10 using Android Studio. All working fine and already tested with physical Android Device. Now it is the time to test IOS device. There's the problem started.
I can't build my project in XCode. I already changed user defined build settings as shown in screenshots
When build the project, it is still finding the flutter SDK location of Windows OS
This is my flutter doctor check in macOS
Please guide me.
I found the solution with the help of my friend - flutter developer.
Go to the project directory and run flutter create -i swift . It will recreate the ios folder in project.
Then run pod install command under ios folder
Android Studio 4.2.1 on Windows 10. Latest stable Flutter version.
If I create a Flutter project I have no database inspector, no profiler and no emulator window, no evd manager under tools menu. Also Device File explorer is gone and i cannot search my database adb file.
Flutter doctor gives no error.
Everything worked fine until the upgrade to 4.2.1
What’s going on? how can i get those tools back? Thank you
This is my very first flutter project. I do not have Mac pc/desktop . Sources from web instructs to approach rental methods. I cannot afford those techniques. I have to add IOS app using android studio or Vs Code. Help me out please
It's not possible add iOS to flutter without install xcode in your machine, so you need run project with mac OS
But for learning purpose you can install mac os on VMware and develop on it, but for publish app on itune store you need export binary from physical mac computer.
I have tried this 3 or 4 times, but it seems like the only version is MAMP pro, every time I install the .pkg file, it installs MAMP pro, the MAMP standard and pro version seems (according to the docs) to be bundled together with the pro version. The docs say the standard version will work after the demo pro expires but all it does it lock down the entire app.
"This download package for Mac OS X contains the free MAMP and a free 14-day trial of MAMP PRO. MAMP can be used stand-alone without MAMP PRO."
^ Does this "stand-alone" even exist?
I selected customize, and I un-checked the Pro version but it does not do this. Every time I launch the app I have a demo expired error.
MAMP.app (the thing you need) is buried inside of the MAMP/ folder (unlike the pro version) so if you are good at where's waldo, then you won't have any trouble since its in a folder with dozens of other things that all render the same looking on Mac. PC users probably don't have this issue.