Folder Structure
Google code
The google paths do not work, I CAN get intrafolder imports working, but nothing from outside. Added the name from pubspec, not importing. Any ideas, I am rapidly going insane! The first package import is the google code not edited, second is me trying to get it to work.
Related
I am trying to import SQLite into an app in Xcode. The version of this app was originally developed using SQLite from the following link (not SQLite3).
https://github.com/stephencelis/SQLite.swift
The library has worked in previous iterations, but now I get an error that says "No such module SQLite" when I try to import the library at the top of the file I want to use it.
I have followed the instructions on the gitHub page and still have trouble with the library. One thing that I notice is that in the file explorer the SQLite.framework files are highlighted in red. I believe this is the source of the problem however, I don't know how to fix this.
File Picture:
Import Error:
It looks like you want to include SQLite into your ReadySetFit project? If so, what you really need to do is to follow the instructions under the "Installation" section found on the GitHub repo's main page. I'm a fan of Cocoapods (because all you'd need to do then is add a Podfile to the folder containing your ReadySetFit project), but there's also SwiftPackageManager or Carthage.
Along with the instructions in the SQLite github repo main page (or README.md), here's a tutorial on how to add a Podfile to your project.
I hope this helps!
Is there any recommendation how to import local files. In my case I would have 2 options:
import 'package:workshop/feed/item.dart';
import 'item.dart';
I haven't found anything on that on the guide Effective Dart: Style nor on Google search.
There are at least two different recommendations, depending on who you ask.
Either works, I personally recommend the latter, shorter, variant.
It is sufficient and it avoids the issue of hard-coding your package name into every file. If you ever want to rename the package, that will be a drudge.
There is one issue which makes some people recommend the former format.
If you import a package library using a non-package: URI, say by having a file in the bin/ or test/ directory do an import like:
import "../lib/mylib.dart";
then that library is now imported using two different URIs:
package:mypkg/mylib.dart and
file:///somewhere/mypkg/lib/mylib.dart
Since Dart identifies libraries by their import URIs, these two imports will be treated as different libraries, each with their own global and static variables, which just happen to have the same source code. That's an annoying problem, and can be hard to debug. If you use the long package:... import everywhere, then at least the issue is restricted to the first library you import. If you use a relative import, import "src/helper.dart";, then that library will now also exist in two versions:
package:mypkg/src/helper.dart and
file:///somewhere/mypkg/lib/src/helper.dart
The real issue here was the first import which contained a /lib/ in the path. You must never have such an import. Using package: URIs for all imports may reduce the issue, but not remove it.
I recommend using the relative path, and making sure that you never have a /lib/ in any import path. Libraries in the /lib/ directory of a pub package are package libraries and should be referred to using package: URIs. If you do that, then relative URIs will be resolved against the package URI and again be a package URI, and all is well.
I’m using Googles sample app, running from their workspace file, to see how specifically Firebase Authentication works. I downloaded their sample project, installed the CocoaPods via terminal, and have ran Pod Update to ensure everything is up to date.
When I compile everything goes smooth until the very end with a single compiler crash for “No Such Module” for “import FirebaseAuthUI”.
I can post the code when I get home, and feel there may be something wrong with the header search path in build settings, have tried adding $(SCROOT) and continues to have an issue finding the frameworks.
I’ve scoured the net and have seen other issues finding Firebase pods just like this, just wondering what could be wrong. Here is a link to the project, I have not modified this project at all. Just wanted to see it work.
https://github.com/firebase/friendlypix-ios
FirebaseAuthUI & FirebaseGoogleAuthUI are now part of FirebaseUI.
So you should replace all the import FirebaseAuthUI & import FirebaseGoogleAuthUI with import FirebaseUI
You will be ready to go.
I'm currently studying the source code of Firefox-iOS app by creating my own Swift project and typing the code line by line.
In one of the source code files, it imported a packaged named Storage
But I don't think the package Storage is part of the apple API and I don't really know how I can import it.
Edit
Multiple podfiles are present in the project folder
In Swift you dont import other Swift files as they are readily available to use directly.
But you need to import another module. It looks like Storage here is a module inside the firefox-ios app workspace and hence you need to import it before using it.
I looked at the sourcecode at Github and it does contain a package named Storage.
You can read this to understand more about Modules and import statement.
I am trying to import the NYXImagesKit library in to my iOS 5.1 project but it will not show up as importable code. It cannot find the library. I have dragged the NYXImagesKit library in to the project and added the libraries. I have also added the following to my build phases:
However I still get an error saying it cannot find NYXImagesKit.h when i try to import it.
NYXImagesKit can be found from here: https://github.com/Nyx0uf/NYXImagesKit
Ive used this in a previous project so I know that it works.
screenshot of location of .h file:
header search paths:
You are not having an issue with "importing" the library proper. (I would not like to appear pedantic, but a library is linked, not imported). The issue you are having is with the header file which comes with the library.
To fix it, you should make sure to add the path to NYXImagesKit.h in your project build sentting (Search Headers Path). This can by found under Build options in your project settings.
Alternatively, an easier way is to add the NYXImagesKit.h file to your project (like any .m file). Then it will be found without the need to specify an header search path.
EDIT:
Since from what you report, everything seems ok, he only idea I can come up with is making sure that the paths are defined for your target (as opposed to the project overall); but I guess it is already like that.
Other than that, only resort is thinking that the project got corrupted somehow. You can inspect the project.pbxproj file inside your .xcodeproj document with a text editor and ensure that everything looks fine.
If everything fails, just start over with a new project.