I have installed v. 0.7.2. The problem I found is it has not installed the bubble images which are required to display in current Chat. However, this issue is only on real device and not on the simulator.
I believe that the issue is because of the Bundle images, which is copied on the Simulator but can't be copied on the device.
How to fix it?
@hemangshah Did you add MessageKit via Carthage or Cocoapods? FWIW, your issue may have been fixed in 0.7.4, so check this against the latest release.
Via CocoaPods
On Tue, 26 Sep 2017 at 19:12, Corey Walo notifications@github.com wrote:
@hemangshah https://github.com/hemangshah Did you MessageKit via
Carthage or Cocoapods?โ
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MessageKit/MessageKit/issues/168#issuecomment-332201833,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADKPBDxLDRJHhZBUN9u1kk9nmYn62J9iks5smP8kgaJpZM4PkKP6
.>
Sent from my iPhone
Because @SD10 keeps breaking my images ๐
https://github.com/MessageKit/MessageKit/blob/master/MessageKit.podspec#L19
Needs to be Assets/MessageKitAssets.bundle/Images/*.png
Please update it. My app will be live soon.
On Tue, 26 Sep 2017 at 19:56, James Sherlock notifications@github.com
wrote:
Because @SD10 https://github.com/sd10 keeps breaking my images ๐
https://github.com/MessageKit/MessageKit/blob/master/MessageKit.podspec#L19
Needs to be Assets/MessageKitAssets.bundle/Images/*.png
โ
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MessageKit/MessageKit/issues/168#issuecomment-332215893,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADKPBMmIs7BAV2qFatEnou4sU38TsLkdks5smQmTgaJpZM4PkKP6
.>
Sent from my iPhone
Haven't got time to test the fix myself right now, if someone else wants to have a look.
My app will be live soon
I must admit I find this statement a bit bewildering, considering you raised the bug 2 hours ago
I have completed my app testing on the simulator. Today given for the test
and found this bug. We are planning to live it next week as once our tester
reviews.
On Tue, 26 Sep 2017 at 20:03, James Sherlock notifications@github.com
wrote:
Haven't got time to test the fix myself right now, if someone else wants
to have a look.My app will be live soon
I must admit I find this statement a bit bewildering, considering you
raised the bug 2 hours agoโ
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MessageKit/MessageKit/issues/168#issuecomment-332218083,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADKPBA2APNYtUkC9CP25zJyt480dyBVoks5smQsegaJpZM4PkKP6
.>
Sent from my iPhone
Did you check the project's description? In-progress
Did you check the project's version? 0.8.2, that means this is not even the first version of the project.
You really shouldn't be using this on production just yet.
Also remember that this is community-driven, that means things will get fixed when people have free time.
If you're already invested and you really need the fix right now, you're welcome to fix it yourself and submit a pull request.
_Edit: Just in case this sounded too harsh, I want you to know that this was not my intent. I'm not a native English speaker, so it's sometimes hard for me to judge how my message will be interpreted._
Hey @hemangshah,
I'm sorry you're experiencing this problem. I'm doing my best to accommodate everyone. The project is not stable but is approaching stability.
Have you tried upgrading to v0.8.2 and seeing if your problem persists? I think the minimum version to get this working is v0.7.4.
@SD10, I have upgraded to 0.7.4 and now I can see the resources added to my project. I will update here once I will check whether it's working on the device or not. However, thank you so much for your quick fix and solution.
@NinoScript, Thanks for putting a note in the end else I might poke you ๐ Anyways, yes, you're right. I highly understand how's @SD10 and other contributors working in their spare time (actually they are maintaining some spare time for this library and for the issues raised). I can surely contribute to any of the issues I found as far as I really know a fix, I am the developer who likes to contribute in writing some new code and I really don't want to fix this CocoaPods (or Podspecs) issues as I am really not good at it yet. Btw, I really don't mind to use a repo which is in-progress but approx. 940+ developers liked it and shown their interest. I am one of the developers. When we use an in-progress library we are the people who will experiment it in different ways then the owner of this repo predicts. So it will be really a good chance to find out the issues and be able to fix it (only if they want, we are not forcing to fix it, and we have other choices too). So in short, if they can provide an immediate fix or support it will help all the developers and we will be really happy to come back and contribute whenever it's possible and in our hands. To all the contributors and specially @SD10 @fbartho @Sherlouk and you, you guys are doing a fantastic job !! Keep doing it until it's really possible for you. You're making us happy. Have a nice day!
@hemangshah We appreciate you using the project because as you said it allows us to figure out what we need to improve ๐ Thank you for your patience and understanding
Most helpful comment
Did you check the project's description?
In-progressDid you check the project's version? 0.8.2, that means this is not even the first version of the project.
You really shouldn't be using this on production just yet.
Also remember that this is
community-driven, that means things will get fixed when people have free time.If you're already invested and you really need the fix right now, you're welcome to fix it yourself and submit a pull request.
_Edit: Just in case this sounded too harsh, I want you to know that this was not my intent. I'm not a native English speaker, so it's sometimes hard for me to judge how my message will be interpreted._