As I can see there are multiple complains already filed against not updating changelog/overview, this problem exists in their side, Cocoapods team is working on it but it is not fixed. (existing complains- https://github.com/CocoaPods/cocoadocs.org/issues/589) .
There is a webhook present to update the same but that is only for open-source projects but I own a private project, I am not able to change the overview page.
Admob has removed all the changelog and readme from their cocoapod and put a short version independent snippet(ref:-https://cocoapods.org/pods/Google-Mobile-Ads-SDK)
I am also trying to do the same, can anyone help me how to update the same?
Related
I am using Xcode 9.4 and current react native version #0.54.4 I want to upgrade the version to 0.55.4.
As I upgrade my project using react-native-git-upgrade, I see some un merged conflicts in the project.pbxproj. Some of the settings are my own that are conflicting with the changes in the new version.
I tried all the possible ways in which I could resolve the conflicts. But still X-code shows the error could not load the project, and it does not allow me to build my project.
How do I understand what those conflicts are referring to and how can I safely resolve the conflicts?
Unfortunately there is no magic way to resolve conflicts. I wish there was. The file is managed by Xcode and from personal experience I have found that you can easily mess it up performing merges.
Git is definitely your best-friend. Make sure that before you start any merge you are on a new branch and fully committed so that if you mess-up you can easily get back to your original version.
What I usually do is keep the original version of the project.pbxproj and then make the changes manually in Xcode. I know this doesn't sound ideal but it does mean you should be able to open the project in Xcode, though your project may not run - just yet.
If you’re unclear about which version to keep, I would keep ours as that is the original version of your project.pbxproj. From the documentation:
You can think of "ours" as "your team" and "theirs" as "the React Native dev team".
Then I would make the changes manually as detailed below. As that will show their changes and the should hopefully not be that many.
To help me find the changes that I have to make I find that React Native Upgrade Helper is an invaluable resource. There you can find a git diff of any two versions of react-native that you choose. (This saves you having to create two projects and then compare them yourself, a big timesaver.)
Currently you are upgrading from 0.54.4 to 0.55.4 this link shows the diff between those versions
https://react-native-community.github.io/upgrade-helper/?from=0.54.4&to=0.55.4
For additional help you could create a project in a specific react-native version, using the following will create a project for version 0.55.4.
react-native init newproject --version react-native#0.55.4
That way you can look inside the Xcode project to see what has been added, and where it was added from, as the git diff doesn't always tell where it came from.
I have never had much luck using react-native-git-upgrade and I have come to prefer doing it manually, as I have had much more success doing it that way.
After updating react native to version 0.55 from 0.51, everything seemed to function normally in the local mode. But the production build fails.
I fixed this by upgrading react native once again from 0.51, and keeping my changes instead of theirs almost all the time.
May be there should be more detailed explanation in the documentation regarding the kind of issues one run into, by picking the wrong changes.
I'm currently working on a iOS (Swift) app for which I installed a few Frameworks via Cocoapods.
I have been facing a few issues with one of the frameworks and decided to tweak its code manually to run some tests and see if I could make things work.
I ended up figuring out a way to achieve what I wanted but I had to add a couple files in that framework as well as modify a few others.
This is the first time I do this and I'm almost certain this is no the best way to do things but I wanted to get some advices on how I can maintain that framework (that is behaving the way I want) in the future?
If I run "pod install" again, I suppose the framework and my changes will be overridden...
Any advice would be really appreciated.
Find the source repo (probably on GitHub) and fork it to your own account. Check out that repo and make your changes.
Optionally I would recommend making your adjustments to the code reusable so others can also use your tweaked version (make it configurable so they can turn the additional functionality on or off) and then submit a pull request back to the original repo.
If you don't want to do that you can point your Podfile directly to your customised repo using the following format:
pod 'Alamofire', :git => 'https://github.com/Alamofire/Alamofire.git'
Or you could look at creating your own CocoaPod (either by publishing to CocoaPods public specs repo or creating your own specs repo).
This post is in regards to two Cocoapods of which I am the owner of:
https://cocoapods.org/?q=id.me (There's only one cocoapod that shows up and I can't link to it because it's broken)
https://cocoapods.org/?q=idmeweb (There's only one cocoapods that shows up and I can't link to it because it's broken).
I need the first CocoaPod (which has already been deprecated), ID.me WebVerify to be completely removed as it's podspec points to a personal repo of mine, http://github.com/artsabintsev/Harpy/. The actual location it should have pointed to no longer exists, and my previous employer, ID.me, has asked me have it removed.
I need the second CocoaPod, https://cocoapods.org/pods/IDmeWebVerify, to work. Apparently, clicking on the link does nothing. My previous employer, ID.me, has asked me to figure out how to get it fixed.
Thank you for any and all assistance.
There are pod trunk x commands to deprecate and delete if you have admin access to them.
I am developing an app using nativescript with AppBuilder and Visual Studio. I am using a plugin called nativescript-pdf-view (https://github.com/Merott/nativescript-pdf-view). Everything worked fine until Apple changed one of their methods in xCode 8. See http://fluentreports.com/blog/?p=401 for details.
I have submitted a question to the author of the plugin 5 days ago, but have not received an answer yet, so I decided to make the change in the plugin code myself. The change is very simple, but after the update when I load the app to my test device, I still get the same error.
My question is: How does AppBuilder build plugins? Is it enough to update source code of the plugin to update it? How can I force the AppBuilder to rebuild this plugin?
I have a feeling the the plugin is cached somewhere because I get the same error message and stack trace even though the source code is changed.
Any suggestions are greatly appreciated.
In order to use a custom plugin in your project you have to update the reference in your package.json. For example in your case, you can:
Get the source code of nativescript-pdf-view.
Fix the issue you've noticed.
Build a .tgz from your modified source code (npm pack command should help you to create a .tgz).
Include the .tgz in your project (for example at the root level, right next to package.json).
Reference the .tgz in your package.json, so instead of having "nativescript-pdf-view": "1.0.0", you should have "nativescript-pdf-view": "file:nativescrip-pdf-view.tgz".
Build your project.
This way the custom plugin will be used instead of the one from npm.
There's no caching of plugins in the cloud builds. The process uses your package.json to install required dependencies.
In my project I am having a problem with the fbsdk. Upon linking the fbsdkcore to my project in xcode using the rnpm as shown here: https://facebook.github.io/react-native/docs/linking-libraries-ios.html
My build now fails due to my RCTFBSDKCore cannot find the RCTBridgeModule.h, even though I think I have gone through all the neccessary steps to include this, even in the Header Search in build settings as shown below:
Linking Binary w/ Lib:
And the Header Search:
After this I am quite lost. I have also tried to update all of my packages without success. And as one can see in the picture below, I have two fbsdkcore, is this one too many, because it is only when I try to build the RCTFBSDKCore that it fails, it is successfull in the other case.
Ok, so to my question. Could it be that the library should not be included like that in the first place? If not, what have I done wrong/missed?
rnpm does not support linking multiple libraries at the moment. Check this article for setting up RN & fbsdk.