I'm following this tutorial here:
https://docs.aws.amazon.com/appsync/latest/devguide/building-a-client-app-ios.html
I'm having some issues getting it to work, wondering if anyone has a working example.
Current issues:
Pods don't match up to the tutorial (awss3 and awsappsync require
different versions of AWSCore (2.6.6 vs 2.6.12)
When using using different pod versions (apsync 2.6.7 and awss3 2.6.6) - the code generated by api-appsync-codegen
doesn't compile - it doesn't create an S3Object class - but tries to
extend it.
Thanks for the help.
AppSync SDK release of 2.6.14 fixes this issue. Now it takes dependency on latest available version of code. You should be able to run pod install --repo-update and be able to get the latest installation.
Thanks,
Rohan
Related
We've just upgraded from Airflow 2.2.4 to 2.4.2, which we deploy via k8s and Helm, using the base apache-airflow==2.4.2 Docker image with some other Python packages installed with pip. Part of Airflow 2.4.2 upgrade replaces Tree View with Grid View in the web UI. When we go to Grid View, we see the following:
The marked up output is your generic Airflow error:
Ooops!
Something bad has happened.
Airflow is used by many users, and it is very likely that others had
similar problems and you can easily find a solution to your problem.
Consider following these steps:
gather the relevant information (detailed logs with errors,
reproduction steps, details of your deployment)
find similar issues using:
GitHub Discussions
GitHub Issues
Stack Overflow
the usual search engine you use on a daily basis
if you run Airflow on a Managed Service, consider opening an issue
using the service support channels
if you tried and have difficulty with diagnosing and fixing the
problem yourself, consider creating a bug report.
Make sure however, to include all relevant details and results of your investigation so far.
Python version: 3.9.15 Airflow version: 2.4.2 Node:
{{deprecated by author}}
------------------------------------------------------------------------------- Error! > Please contact server admin.
Looking in our web logs only yields the following text:
[[34m2022-12-15 01:31:52,943[0m] {[34mapp.py:[0m1741} ERROR[0m - Exception on /object/grid_data [GET][0m
I can't find any other instance online of another Airflow user experiencing this problem, despite searching for hours.
What could be the problem here? It appears to be an internal Airflow UI issue, so may be related to our infrastructure or setup perhaps, but I can't see why.
Also of note, some users had trouble with Grid View when the Operators in their DAGs had a parameters named params. I can rule this out as a cause, as our DAGs and Operators definitely do not have that.
How exactly did you make the update? Did you run helm uninstall airflow and then helm install apache/airflow?
Did you check that run migration job succeed or even if it was executed?
Looks like the issue was to do with dbt-snowflake==1.0.0 being installed as well, and it had some sort of Python package constraint conflict with apache-airflow==2.4.2. Upgrading dbt-snowflake to v1.3.0 solved the issue.
Earlier was using 5.7.0 but there are some issue related to firebase storage. to find the solution of this I read somewhere that I need to update the firebase with latest version i.e 5.12.0 Or greater.
I am updating a new version but facing "framework not found MeasurementNanoPB" error. Search a lot regarding the same but no solution found.
There are no relavent steps, anyone who have updated firabse with latest version might have received the same error.
Tried manually installing the firebase sdk.
Resolved!
Tried deleting Pod.lock file, removed all the pods related to firebase from the Podfile. install pod without firebase. When it is done, add all the pods one by one for firebase.
It still gives an error for "GRPCClient not found". Add below framework in Podfile.
pod gRPC-ProtoRPC.
Then got error for "measurement nanopb.framework" not found so just follow below steps:
1) Clean project
2) Remove derived data from respective folder
3) Now search for "nanopb" in whole project(you will find under OtherLinkerFlags) and remove it.
4) Now Install POD again.
And you are done. Now the project will run without errors.
According to https://firebase.google.com/support/release-notes/ios
Version 5.14.0 - December 4, 2018, fixes this:
The FirebaseAnalytics CocoaPod corrects its dependency on the GoogleAppMeasurement CocoaPod (#2151).
Did you try to update to Firebase 5.14.0 ?
Otherwise, did you try to include pod 'Firebase/Performance'in your podfile ?
After upgrade to sdk 2.5.216 and runtime 5.5.216 Test-ServiceFabricApplicationPackage command works only for complete package. In case of partial app upgrade (some Pkg are removed) it results in "Windows PowerShell has stopped working". I have tested on several computers and several apps. to reproduce:
create test app with 2 services and deploy.
change app version and particular service version.
create package and remove Pkg folder from it for the service without modifications.
connect to Service Fabric and test like Test-ServiceFabricApplicationPackage -ApplicationPackagePath "..path" -ImageStoreConnectionString "fabric:ImageStore"
Maybe somebody was able to overcome this issue? or at least has similar behavior so I'm not alone in Universe.
Thanks!
Alex
Take a look at https://github.com/Azure/service-fabric-issues/issues/259
This is a bug in our code. It happens when a compressed package was uploaded and provisioned in the cluster. Testing a new version of the application fails because settings file was not found in the provisioned version.
We fixed the issue and it will become available in one of our next releases.
Meanwhile, you can skip compression or test the version 2 application package without passing in the image store connection string.
Apologies for the inconvenience!
Two part question:
How does one get the currently installed version of Realm in code? Swift 3, macOS. I was unable to location any Realm.version property - perhaps I overlooked it.
In a related question
What is the solution to upgrade Realm to the latest version within a project? After updating CocoaPods to the latest, and refreshing, pod install doesn't appear to update Realm. I have 2.0.3 installed and 2.2.0 is available.
If you're embedding Realm Swift as a dynamic framework directly, the version number is contained in the framework's info.plist file. It should be possible to access the plist during runtime; there's a few answers on SO discussing this.
Since CocoaPods creates dynamic frameworks for Swift, the above approach of accessing the info plists should work, but if it doesn't there might be other ways to access versions of pods.
In any case, I would definitely recommend you review why you're wanting to check the version numbers of your libraries. It's better practice to check a framework's capabilities at runtime (eg, testing a class you need exists etc) than to directly use the version number.
For your second question, you need to run pod update RealmSwift to get CocoaPods to check for an updated version of Realm.
I'm trying to deploy using firebase 3.0.0 latest CLI version.
Unfortunately I get this errors:
Error: Unable to authorize access to project XXXX
Note: This version of the Firebase CLI is only compatible with projects upgraded
to the new Firebase Console. To access firebase.com apps, you will need to
use a previous version: npm install -g firebase-tools#^2.1
Any ideas?
As a matter of fact I was trying to deploy to a custom domain that was not yet verified.
My bad :(
Sorry guys.
I believe you need to upgrade your project to the new Firebase at firebase.google.com. If you haven't you should check out the announcements at Google I/O 2016.