Originally created by @Plnda on GitHub (Jul 6, 2017).
do {
try CoreStore.perform(synchronous: { transaction -> Void in
// Delete the current user data
transaction.deleteAll(From<User>())
var avatarString = tripleAUser.avatarURI
if !avatarString.contains("https:") {
avatarString = "https:" + avatarString
}
// Create a new user
let user = transaction.create(Into<User>())
user.identifier = Int64(tripleAUser.id)
user.name = tripleAUser.name
user.email = tripleAUser.email
user.avatar = avatarString
})
} catch _ {
print("error")
}
Originally created by @Plnda on GitHub (Jul 6, 2017).
do {
try CoreStore.perform(synchronous: { transaction -> Void in
// Delete the current user data
transaction.deleteAll(From<User>())
var avatarString = tripleAUser.avatarURI
if !avatarString.contains("https:") {
avatarString = "https:" + avatarString
}
// Create a new user
let user = transaction.create(Into<User>())
user.identifier = Int64(tripleAUser.id)
user.name = tripleAUser.name
user.email = tripleAUser.email
user.avatar = avatarString
})
} catch _ {
print("error")
}
@Plnda I can't tell with just this code, can you give other info? Have you found through Instruments what objects/types are getting leaked?
@JohnEstropia commented on GitHub (Jul 6, 2017):
@Plnda I can't tell with just this code, can you give other info? Have you found through Instruments what objects/types are getting leaked?
@Plnda Have you resolved this issue? I will close this issue as irreproducible as I can't see this happening on the demo app.
@JohnEstropia commented on GitHub (Jul 15, 2017):
@Plnda Have you resolved this issue? I will close this issue as irreproducible as I can't see this happening on the demo app.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Plnda on GitHub (Jul 6, 2017).
@JohnEstropia commented on GitHub (Jul 6, 2017):
@Plnda I can't tell with just this code, can you give other info? Have you found through Instruments what objects/types are getting leaked?
@JohnEstropia commented on GitHub (Jul 15, 2017):
@Plnda Have you resolved this issue? I will close this issue as irreproducible as I can't see this happening on the demo app.