Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3.18.0 crashes on some devices #6257

Closed
lszzy opened this issue Sep 23, 2019 · 5 comments · Fixed by #6309
Closed

3.18.0 crashes on some devices #6257

lszzy opened this issue Sep 23, 2019 · 5 comments · Fixed by #6309

Comments

@lszzy
Copy link

lszzy commented Sep 23, 2019

Before the 3.17.3 version, the function has been running normally. After the 3.18.0 was online, some devices received feedback flashback. The code has not been changed. The check found that the problem is caused by the 3.18.0 version.

Goals

Expected Results

Actual Results

Steps to Reproduce

Code Sample

Cart *cart = [Cart objectForPrimaryKey:@(shopId)];
if (!cart) {
RLMRealm *realm = [RLMRealm defaultRealm];
[realm beginWriteTransaction];
cart = [[Cart alloc] init];
cart.shop_id = shopId;
[realm addObject:cart];
[realm commitWriteTransaction];
}
return cart;

It Crashes at [realm addObject:cart]; since version 3.18.0

屏幕快照 2019-09-23 上午10 45 41

屏幕快照 2019-09-23 上午10 46 43

Version of Realm and Tooling

Realm framework version: ?
3.18.0
Realm Object Server version: ?

Xcode version: ?
10.3
iOS/OSX version: ?

Dependency manager + version: ?

@jeandigiovanni-next
Copy link

Hello,

I think we have the same issue on our side. Some devices have this crash after updating our app.
We updated Realm from 3.14.0 to 3.18.0

Capture d’écran 2019-10-02 à 11 57 20

Realm framework version: 3.18.0
Xcode version: 11.0
iOS/OSX version:
Capture d’écran 2019-10-02 à 11 58 47

Dependency manager + version: Cocoapod 1.8.1

Hopefully these information can help fix the issue.

@andreadelfante
Copy link

andreadelfante commented Oct 4, 2019

Hi,
I got this issue too! Does anyone have an idea about why this crash happens after the upgrade?

@DavidFafinski
Copy link

DavidFafinski commented Oct 17, 2019

Hello,
Same problem here :( please send help.

@aliabbas90
Copy link

aliabbas90 commented Oct 17, 2019

Hello,
Any update for this issue ? We are encountered the same issue.

@tgoyne
Copy link
Member

tgoyne commented Oct 17, 2019

This is probably the same thing as #6268, as there's only one other assertion in that function. We will hopefully have a release out fixing that early next week.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants