bumptech / bump-api-ios Goto Github PK

When there is no internet connection then if bumpclient disconnect is called then it crashes the app.

Hi,

I wanted to know how to tear down/disconnect the bump channel so another bump can occur, after previously already accepting a channel match?

After an initial match confirm, the clients talk to each other and may realise they don't want to be connected anymore.

I assume I can use the bumpClient disconnect method, however this method seems very flakey and confusing.

1. I will receive a crash in bump's library after reconnecting a few times
2. It seems very flakey, later bumps are supposedly detected but none of the channel match logic gets to run to confirm the connection

I get the feeling the library is not 100% stable/complete right now?

Thanks,
Andrew

I am calling [[BumpClient sharedClient] disconnect] in viewWillDisappear in screen navigation ;
But "disconnect" does not works.I also called this method in viewDidDissapear on screen navigation.Once you shared data with any person & navigation screens and after you again wants to share data with that person , Bump api does not works as it should. I am using Bump since last 16 months , So at least you should update all codes.
Thanx.

I believe it simply needs a recompile that includes that architecture.

Report from https://groups.google.com/forum/#!topic/bump-api/uS0LOX5RaM0

I'm testing out Bump API v3.0.1 and the BumpTest app consistently crashes when the Bump client is being configured.

[BumpClient configureWithAPIKey:@"[my api key]" andUserID:[[UIDevice currentDevice] name]];

causes the app to crash if the wi-fi network I'm on is blocking the bump server. With the previous API, I'd be able to recover, but in the new API, my app just crashes and burns. I could check for network availability to the Bump server, but this also seems like the Bump API should handle this scenario.

Hi!
About a month ago I tried to add a bumping ability to the my application, but all the time after some first BumpAPI initializing functions were called the app crashed with very strange behavior - it seemed there was a stack corruption or something like that. I debugged the app for a couple of days but could not find the reason of the crash - the only thing I noticed that the newly created application with only BumpAPI added worked well. Then I looked through the symbols table of libBump.a and got the reason! I noticed that you used the same SHA1 lib that I did and the final application's binary had a double of those SHA1 functions, but I didn't have any warnings regarding this from compiler. And as a result it seemed the execution flow went wrong and I had that strange crash without any information what went wrong. So, I just changed names of SHA1 functions from my lib (I added prefixes) and everything started working well!
So, something like a petition for the future :-) Could you please change names of your SHA1 lib (and other public libs you use) in order not to have the issues like that? :-)
Thanks in advance!

I think that would be a nice to have a progress block in the -[BumpClient sendData:toChannel:] in order to be able to track and show to the user the send progress.
I expect the same when I receive the data: it would be nice to be able to set a callback block to show the download progress.

Trying to send a large file ~1Mb I got an assertion fail, specifically Assertion failed: ([data length] < MAX_BAM_PACKET_SIZE).
I haven't seen anywhere documented this limit.

Since this limit exist we should aware of how much this is or have a method to check if the [NSData length] exceed this limit. I understand that you may want to keep this size hidden and / or be able to change this in the future but you can provide a method like + (BOOL)dataLengthExceedMaxPacketSize:(NSUInteger)dataLength.

I am developing a program in which using two API-keys is necessary. When I try to change the key or set nil as the key the app gets terminated with an error. I get the following message in the console:

Assertion failed: ([apiKey isEqual:key]), function +[BumpClient configureWithAPIKey:andUserID:], file /Users/tg/Documents/iAPI/Bump/BumpClient.m, line 448.

Could you please help me with this problem.

This would be useful! cocoapods.org

I can't get it working, normal?

I am getting a warning from Xcode when I integrated BUMP API. The warning is : "libBump.a (boss.pb-c.o) object file doesn't contain DWARF debug information"

Hello!

I've spent last few days debugging an issue with libbump. There seems to be a problem with handling disconnects and connection availability in the library. Trying to call configureWithAPIKey:andUserID: without Internet connection available results in a crash. Calling disconnect without Internet connection available - crash. Configuring a lib successfully and there's a loss of Internet connection - app starts to consume lots and lots of memory and gets killed by the OS.

It really gets in the way of reliability of the app. With current behaviour you can't just configure lib, use bump feature and leave libbump's connection open, hoping that you'd have Internet connection working ok for all the time you use the app. In long-use scenarios it simply is not reliable enough and won't work.

Please, can you look into this for a next release of the lib?

Issue is reproducible with versions 3.01 and 3.1b2.

Hi
I am new user to use bump api, when bump setconnectionStateChange call back get bump disconnected can we do something to get bump reconnect, or only waiting the bump reconnect by itself

How to close shake sound when bump?
Would you like provide an interface which can close and open shake sound when bump?

Hi, I get this warning when I compile using the lib!

warning: (armv7) /Users/allaire/Lubie/hermes/libBump/libBump.a(boss.pb-c.o) object file doesn't contain DWARF debug information

Any clues?

Thank you!

Test case:
[[BumpClient sharedClient] connect];
[[BumpClient sharedClient] disconnect];
[[BumpClient sharedClient] disconnect]; // <- crash here

Desired behavior:
BumpClient should internally care about it

I only see connect and disconnect methods. It would be good if we have a getter isConnected to check if the client is connected or not.

Also, is there a way to check if the service is up and running. Today, it's taking looong time to change to status "Connected" and sometimes it just doesn't happen.

Thanks.

The libBump 3.1 doesn't compile for iOS Simulator.

0  0x10fea2098  __assert_rtn + 144
1  0x10fea5431  mach_o::relocatable::Section<x86>::addRelocFixup(mach_o::relocatable::Parser<x86>&, macho_relocation_info<Pointer32<LittleEndian> > const*) + 1781
2  0x10feb5636  mach_o::relocatable::Section<x86>::makeFixups(mach_o::relocatable::Parser<x86>&, mach_o::relocatable::Parser<x86>::CFI_CU_InfoArrays const&) + 90
3  0x10feb1aad  mach_o::relocatable::Parser<x86>::parse(mach_o::relocatable::ParserOptions const&) + 1433
4  0x10fea90c3  mach_o::relocatable::Parser<x86>::parse(unsigned char const*, unsigned long long, char const*, long, ld::File::Ordinal, mach_o::relocatable::ParserOptions const&) + 313
5  0x10fea6aa1  mach_o::relocatable::parse(unsigned char const*, unsigned long long, char const*, long, ld::File::Ordinal, mach_o::relocatable::ParserOptions const&) + 149
6  0x10fec733a  archive::File<x86>::makeObjectFileForMember(archive::File<x86>::Entry const*) const + 794
7  0x10fec6e4f  archive::File<x86>::justInTimeforEachAtom(char const*, ld::File::AtomHandler&) const + 139
8  0x10fed8b06  ld::tool::InputFiles::searchLibraries(char const*, bool, bool, bool, ld::File::AtomHandler&) const + 210
9  0x10fedf978  ld::tool::Resolver::resolveUndefines() + 200
10  0x10fee18a3  ld::tool::Resolver::resolve() + 75
11  0x10fea2380  main + 370
12  0x10fe93cd4  start + 52
A linker snapshot was created at:
    /tmp/BumpTest-2013-05-06-140407.ld-snapshot
ld: Assertion failed: (src.atom != NULL), function addRelocFixup, file /SourceCache/ld64/ld64-136/src/ld/parsers/macho_relocatable_file.cpp, line 5468.
clang: error: linker command failed with exit code 1 (use -v to see invocation)